[
https://issues.apache.org/jira/browse/TS-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617856#comment-14617856
]
Bryan Call edited comment on TS-3693 at 7/8/15 2:20 AM:
--------------------------------------------------------
So you are saying that every intercept plugin needs to check that configuration
values or have a separate configuration value and handle the 100-continue logic
itself based on that setting?
was (Author: bcall):
So you are saying that every intercept plugin needs to check that configuration
values or have a separate configuration values and handle the 100-continue
logic itself based on that setting?
> 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)
