[
https://issues.apache.org/jira/browse/TS-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610396#comment-13610396
]
Uri Shachar commented on TS-1125:
---------------------------------
AFAIK -- no browsers actually use "Expect: 100-Continue", but many other
clients do (for example, cURL, .NET clients, adobe downloaders when not
configured with explicit proxy...)
It's quite hard to implement support for this correctly in a proxy perspective
(Squid didn't support this until 3.2) - If you return a 100-Continue
immediately (regardless of upstream), you run into issues if the upstream
refuses the request....
Note that according to the RFC, clients which have seen a 100-Continue response
from a particular upstream are allowed to hang indefinitely while waiting for
the response -- if they haven't seen such a response in the past they "SHOULD
NOT"...
> 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
> Fix For: 3.3.3
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
