[jira] [Commented] (TS-3693) Move 100-continue logic to read client header for intercept plugins

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14609150#comment-14609150 ] 

ASF subversion and git services commented on TS-3693:
-----------------------------------------------------

Commit cc07927fc9780ed3999fc6b3809ac33c5b562e7a in trafficserver's branch refs/heads/master from [~ffcai]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=cc07927 ]

TS-3693: Move 100-continue logic to read client header for intercept plugins


> 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)