[
https://issues.apache.org/jira/browse/TS-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622398#comment-14622398
]
Sudheer Vinukonda commented on TS-3693:
---------------------------------------
[~bcall]: OK, now, as I've been trying to get the message across - we now
actually see an issue because of this. We have an use case, where an encoder
client sends a PUT w/ Expect:100 CONT and we return a 401 (at
READ_REQUEST_HDR_HOOK) to force the client to come back w/ basic auth info
(login/password). With the change here, there's a 100 CONT before the 401
response and the encoder starts uploading the data and it gets messed up when
it sees the 401 right after. This breaks our client and is definitely very bad
for our use case. I recommend to revert this change.
> 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)
