You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/03/22 16:15:16 UTC
[jira] [Commented] (TS-1708) Using tr-pass port option causes
requests with large headers to hang
[ https://issues.apache.org/jira/browse/TS-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610365#comment-13610365 ]
ASF subversion and git services commented on TS-1708:
-----------------------------------------------------
Commit ec019615ff15894e01b91ea7b593a76534883b3b in branch refs/heads/master from Uri Shachar <us...@apache.org>
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=ec01961 ]
TS-1708: Using tr-pass port option causes requests with large headers to hang
If 4KB of headers are read and we haven't decided on requets validity yet, disregard
tr-pass option in order to avoid blocking the writer
> Using tr-pass port option causes requests with large headers to hang
> --------------------------------------------------------------------
>
> Key: TS-1708
> URL: https://issues.apache.org/jira/browse/TS-1708
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Reporter: Uri Shachar
> Assignee: Uri Shachar
> Fix For: 3.3.2
>
> Attachments: transparent_passthrough_hang.diff
>
>
> When tr-pass is enabled and a request comes in on a new connection with total size of request headers > 4K it will hang in the parser (and never time out).
> In order to support tr-pass, we clone the ua_buffer_reader, but until the parser decides the request is valid/invalid, we do not consume data from the clone. Eventually, the underlying iobuffer fills up and the parser won't be called with the rest of the pending data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira