[
https://issues.apache.org/jira/browse/TS-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617865#comment-14617865
]
Sudheer Vinukonda commented on TS-3693:
---------------------------------------
We should first talk about whether the change here makes for poorer behavior.
To me, it sounds like it does. One could argue that, just like you are pointing
whether every intercept plugin needs to handle this on its own, the new
behavior applies to every use case/deployment that doesn't have the intercept
plugin.
The issue here is not whether it blocks what I'm working on. I have provided my
comments/concerns on the patch and so far, I have not seen a single clean
answer yet that addresses the comments/concerns.
> 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)
