[asterisk-bugs] [JIRA] (ASTERISK-30088) func_curl: Subsequent calls are failing, can't clear headers

[Sean Bright (JIRA)]

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

Sean Bright updated ASTERISK-30088:
-----------------------------------

    Comment: was deleted

(was: Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines)

> func_curl: Subsequent calls are failing, can't clear headers
> ------------------------------------------------------------
>
>                 Key: ASTERISK-30088
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30088
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Functions/func_curl
>    Affects Versions: 16.26.0
>         Environment: CentOS 7 x64
>            Reporter: Luke Escude
>            Assignee: Sean Bright
>
> I [mentioned this|http://lists.digium.com/pipermail/asterisk-dev/2022-May/078636.html] in the asterisk mailing list, but figured other people are likely running into the same issue.
> When altering HTTP headers to make a CURL call, those changes persist throughout the channel's lifespan. Therefore, you need to be careful/conscious of what headers, settings (like timeout), etc. are being set, otherwise subsequent CURL calls can cause weird problems.
> So, I believe there needs to be a CURL_RESET() function that sets ALL curl parameters to "factory default".



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