[
https://issues.apache.org/jira/browse/HTTPCLIENT-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13650729#comment-13650729
]
Oleg Kalnichevski commented on HTTPCLIENT-1350:
-----------------------------------------------
Karl,
This is per requirement of the HTTP protocol, RFC 2616, section 8.2.3
---
Because of the presence of older implementations, the protocol allows
ambiguous situations in which a client may send "Expect: 100-
continue" without receiving either a 417 (Expectation Failed) status
or a 100 (Continue) status. Therefore, when a client sends this
header field to an origin server (possibly via a proxy) from which it
has never seen a 100 (Continue) status, the client SHOULD NOT wait
for an indefinite period before sending the request body.
---
By default HttpClient waits 2 to 3 seconds for the server to respond with
either 100 or 4xx and then proceeds with sending request body.
Oleg
> Expect/continue does not consistently work
> ------------------------------------------
>
> Key: HTTPCLIENT-1350
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1350
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 4.2.5
> Reporter: Karl Wright
>
> Expect/continue sometimes does not wait for the response from the server, but
> just goes on ahead and transmits the entire packet. This breaks posting when
> auth is required and streams are non-repeatable. See the end of
> CONNECTORS-682.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
