[
https://issues.apache.org/jira/browse/TS-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401378#comment-13401378
]
William Bardwell commented on TS-1155:
--------------------------------------
Patch against trunk:
--- HttpTransact.cc 2012-06-26 09:14:47.000000000 -0400
+++ HttpTransact.cc 2012-06-26 09:14:11.000000000 -0400
@@ -5266,7 +5266,7 @@
if ((scheme == URL_WKSIDX_HTTP || scheme == URL_WKSIDX_HTTPS) &&
(method == HTTP_WKSIDX_POST || method == HTTP_WKSIDX_PUSH || method ==
HTTP_WKSIDX_PUT)) {
- if (scheme == URL_WKSIDX_HTTP &&
!incoming_hdr->presence(MIME_PRESENCE_CONTENT_LENGTH)) {
+ if (!incoming_hdr->presence(MIME_PRESENCE_CONTENT_LENGTH)) {
bool chunked_encoding = false;
if (incoming_hdr->presence(MIME_PRESENCE_TRANSFER_ENCODING)) {
> POST requests that are chunked encoding hang when going forward to origin
> over SSL
> ----------------------------------------------------------------------------------
>
> Key: TS-1155
> URL: https://issues.apache.org/jira/browse/TS-1155
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Affects Versions: 3.0.2
> Reporter: William Bardwell
> Fix For: 3.3.0
>
>
> If you make a chunked encoded POST request, e.g.:
> curl -H "Transfer-Encoding: chunked" -d@/etc/ca-certificates.conf
> http://example.com/cgi-bin/cgi.pl
> Where ATS is going forward to the origin over SSL, it junk hangs for a little
> while and ends up returning a 502 response.
> The problem seems to be code at proxy/http/HttpTransact.cc:5273 which only
> checks for chunked encoding when the scheme is http. Just removing the extra
> scheme check makes it work for me.
> I don't know why it has that check, especially since it is checking for http
> or https right before that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
