You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Sudheer Vinukonda (JIRA)" <ji...@apache.org> on 2015/07/18 16:43:04 UTC
[jira] [Reopened] (TS-3693) Move 100-continue logic to read client
header for intercept plugins
[ https://issues.apache.org/jira/browse/TS-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sudheer Vinukonda reopened TS-3693:
-----------------------------------
As discussed with [~bcall], we agree there's a need to revisit this fix to (at the very least) ensure the new behavior is not applied automatically to anyone who uses the "100 CONT" feature.
> Move 100-continue logic to read client header for intercept plugins
> -------------------------------------------------------------------
>
> Key: TS-3693
> URL: https://issues.apache.org/jira/browse/TS-3693
> Project: Traffic Server
> Issue Type: Improvement
> Components: HTTP
> Reporter: Bryan Call
> Assignee: Bryan Call
> Labels: yahoo
> Fix For: 6.1.0
>
>
> From https://github.com/apache/trafficserver/pull/216 :
> Currently, ATS handles "Expect: 100-continue" header in HttpSM::state_send_server_request_header. In intercept plugin case, ATS may have no chance to run into this logic, it handles the header in a later point - HttpSM::state_send_server_request_header. I did not take this into account when I wrote the first patch. Now we have an intercept plugin use case in yahoo, and I think we need to move the handle logic some earlier, right after finish parsing the client request header.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)