[asterisk-bugs] [Asterisk 0018046]: [patch] func_curl CURLOPT likes a querycomponent (+-decoding) hashcompat mode
Asterisk Bug Tracker
noreply at bugs.digium.com
Sun Sep 26 23:01:41 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18046
======================================================================
Reported By: wdoekes
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18046
Category: Functions/func_curl
Reproducibility: always
Severity: feature
Priority: normal
Status: feedback
Asterisk Version: 1.6.2.13
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-09-24 04:16 CDT
Last Modified: 2010-09-26 23:01 CDT
======================================================================
Summary: [patch] func_curl CURLOPT likes a querycomponent
(+-decoding) hashcompat mode
Description:
Hi,
in https://issues.asterisk.org/view.php?id=18037 I've added a QSFIELD
which is pretty much obsoleted by the hashcompat mode of CURLOPT.
However, the ast_uri_decode leaves +'es verbatim in the decoded output,
where I expect them to be decoded to spaces.
The attached patch adds a hashcompat=querycomponent mode that decodes the
pluses properly. (For backwards compatibility the ast_value() works for all
other values.)
Regards,
Walter Doekes
OSSO B.V.
======================================================================
----------------------------------------------------------------------
(0127414) tilghman (administrator) - 2010-09-26 23:01
https://issues.asterisk.org/view.php?id=18046#c127414
----------------------------------------------------------------------
Your "query component" mode is not described in RFC 2396, but only in RFC
1866, which has been marked as obsolete (see RFC 2854, which does not
describe this method). Therefore, you should not be using it in any new
applications.
Issue History
Date Modified Username Field Change
======================================================================
2010-09-26 23:01 tilghman Note Added: 0127414
======================================================================
More information about the asterisk-bugs
mailing list