[asterisk-bugs] [JIRA] (ASTERISK-30340) res_media_cache curl options configureable

[mseif (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-30340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mseif updated ASTERISK-30340:
-----------------------------

    Attachment: curl_config_cache.patch

this patch for loaded config from res_curl.conf when the loading or reload res_http_media_cache.so 
after the patch add section [media_cache] like the

[media_cache]
ssl_verify=no
timeout=190
maxheaders=10

ssl_verify: usage on host is self signed ssl and failed ssl error
timeout: default timeout is 180 then set max integer value
maxheaders: default 8 or set to max integer value


> res_media_cache curl options configureable
> ------------------------------------------
>
>                 Key: ASTERISK-30340
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30340
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Resources/NewFeature
>    Affects Versions: 20.0.1
>         Environment: Playback a media from URL. 
>            Reporter: Joeran Vinzens
>            Assignee: Joeran Vinzens
>              Labels: patch
>         Attachments: curl_config_cache.patch
>
>
> We use the media_cache module to cache media resources from url.
> When doing so, and the media server providing the files hangs, the timeouts within the re_media_cache are too long. In the asterisk there are error logs showing the problems. Since the real issue is not within the asterisk but in the web server ew like to make the asterisk a bit stronger to have more aggressive timeouts and settings within the media_cache module.
> Unfortunately these CURL options are hardcoded within the module itself. there is no chance to change it.
> We asked a developer to make a config file containing the curl options.
> Now we have a first implementation for it, but we want to bring it upstream.
> This feature request is meant to discuss whether we can simply create a PR.
> Our talented developer will respond to this issue as well, if you are interested in this feature.



--
This message was sent by Atlassian JIRA
(v6.2#6252)