[
https://issues.apache.org/jira/browse/TS-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622535#comment-14622535
]
Sudheer Vinukonda commented on TS-3693:
---------------------------------------
But, I have been saying the exact same thing in principle, no? Unfortunately,
the commit was not in our local y% version yet, for me to report the
breakage/issues, so I was talking in theory.
I had finally backported the commit from master into our local y! version last
night to try out, to see if it was actually causing a problem and as I had
imagined, it was breaking the client.
Sure, if there's absolutely no other choice and this can *not* be done by the
plugin directly, I suppose it's alright to use a separate config for this new
behavior (if it's alright with everyone else).
> 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)
