[
https://issues.apache.org/jira/browse/TS-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622732#comment-14622732
]
Sudheer Vinukonda commented on TS-3693:
---------------------------------------
The client is a proprietary encoder that is used in our Video stack. It's not
that it can not handle 401 after 100 CONT - but, it adds a wastage of
bandwidth, coz the client pushes bytes before it aborts. When this happens
every time, it has undesirable consequences to throughput, performance and even
stability even in our tests.
I repeatedly said, sending back a "100 CONT" followed by an error looks
odd/ugly. Fwiw, I can't *imagine* an example of how it would affect the
clients, unless, I actually test it. But, IME, whenever you do something that
seems "bad" in practice, you are bound to break things.
> 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)
