[
https://issues.apache.org/jira/browse/TS-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13971670#comment-13971670
]
Bryan Call commented on TS-1125:
--------------------------------
[~ffcai],
Can you explain why the VC_EVENT_WRITE_COMPLETE event action had to change.
Section of the patch:
{code}
case VC_EVENT_WRITE_COMPLETE:
- // mark the vc as no longer in tunnel
- // so we don't get hosed if the ua abort before
- // real response header is received
- ua_entry->in_tunnel = false;
+ if (t_state.txn_conf->send_100_continue_response == 0) {
+ // mark the vc as no longer in tunnel
+ // so we don't get hosed if the ua abort before
+ // real response header is received
+ ua_entry->in_tunnel = false;
+ }
c->write_success = true;
{code}
> POST's with Expect: 100-continue are slowed by delayed 100 response.
> --------------------------------------------------------------------
>
> Key: TS-1125
> URL: https://issues.apache.org/jira/browse/TS-1125
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Affects Versions: 3.0.2
> Environment: TS 3.0.2 going to Apache 2.2 web server
> Reporter: William Bardwell
> Priority: Minor
> Labels: yahoo
> Fix For: 5.2.0
>
> Attachments: TS-1125.diff
>
>
> Sending a post like:
> POST / HTTP/1.1
> Host: www.example.com
> Content-Length: 10
> Expect: 100-continue
> directly to the web server immediately sends back:
> HTTP/1.1 100 Continue
> And then when the post data is sent, a status 200 response comes back.
> But when going through ATS the "HTTP/1.1 100 Continue" is not sent
> immediately, and instead is sent after the POST data has been received. This
> is legal, but it makes clients that are hoping for a 100 continue to wait a
> little while hoping to get that, ATS should forward that response through
> immediately.
> Note: I see curl using "Expect: 100-continue" with > 1024 bytes of post data,
> but web searching indicates that some Microsoft products also use it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
