[asterisk-bugs] [Asterisk 0012920]: [patch] Added CURL() Function Timeout Argument

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12920 
====================================================================== 
Reported By:                davevg
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12920
Category:                   Functions/func_curl
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 124707 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             06-23-2008 16:12 CDT
Last Modified:              06-25-2008 08:41 CDT
====================================================================== 
Summary:                    [patch] Added CURL() Function Timeout Argument
Description: 
If you have a long running web script the CURL function is currently hard
coded to timeout after 180 seconds.  This patch adds a 3rd parameter to the
function which when set overrides the 180 second default.

Example usage:
exten => 1,1,Set(foo=${CURL(http://127.0.0.1/test.pl,,3)})
Which will set a timeout of 3 seconds on the CURL call.
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 06-25-08 08:41  
---------------------------------------------------------------------- 
On res_config_curl, this may provide the impetus to fix curl within
Asterisk, such that the two modules rely on a res_curl backend module
(which controls the global initialization) and let res_config_curl not
depend upon func_curl (which was always kind of a hack anyway).  The reason
why would be to ensure that if you need different options for
res_config_curl than are needed for CURL queries from the dialplan, that
they don't conflict.  I could see some fairly nasty bugs that could appear
if this was the case, under the current schema. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-25-08 08:41  Corydon76      Note Added: 0089210                          
======================================================================