Summary:	ASTERISK-28236: Support separated HTTP request
Reporter:	sungtae kim (pchero)	Labels:
Date Opened:	2019-01-09 04:26:19.000-0600	Date Closed:	2019-02-26 07:19:29.000-0600
Priority:	Minor	Regression?
Status:	Waiting for Feedback/In Progress	Components:	Core/HTTP
Versions:	16.1.1	Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Currently, the Asterisk does not support separated HTTP request. If the HTTP request divided into more than 2 messages, it response error. And it accepts only 4KB of message body. If the Asterisk accepts separated HTTP request and more length, it could be better. For the longer length, for example, asterisk accepts /channel/<channel id>/play ARI command with array of "media"s. The media might be string of URI. With current situation, the user can't set many 'media's if uri length is long.
Comments:	By: Asterisk Team (asteriskteam) 2019-01-09 04:26:20.583-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: Friendly Automation (friendly-automation) 2019-02-26 07:19:30.335-0600 Change 10869 merged by Friendly Automation: http.c: Support separated HTTP request [https://gerrit.asterisk.org/10869|https://gerrit.asterisk.org/10869] By: Friendly Automation (friendly-automation) 2019-02-26 07:32:27.054-0600 Change 11010 merged by Joshua C. Colp: http.c: Support separated HTTP request [https://gerrit.asterisk.org/11010|https://gerrit.asterisk.org/11010] By: Friendly Automation (friendly-automation) 2019-02-26 07:39:25.528-0600 Change 11026 merged by Joshua C. Colp: http.c: Support separated HTTP request [https://gerrit.asterisk.org/11026|https://gerrit.asterisk.org/11026] By: Joshua C. Colp (jcolp) 2019-02-28 05:32:16.034-0600 This change does not appear to work under Asterisk 13, and causes failures. You can see them at: https://jenkins2.asterisk.org/job/asterisk-periodics-daily/job/13/239/#showFailuresLink Specifically all the ARI failures. I narrowed it down to this change, which I now have a revert up for. Running manually shows that the code expected to read a set number of bytes, but got 0 and thus failed.