2ae703aa85
to the caching module, but the original request did not expect one, it's acceptable for the caching module to throw an exception but it had better consume the body of the 100 (Continue) response before doing so to ensure proper release of resources. Encountering this would require the underlying (non-caching) HttpClient to not handle the expect-continue handshake properly *AND* for the origin server to send a 100-Continue response out of turn *WITH* a response body. Highly unlikely, but at least this codepath is covered properly now. git-svn-id: https://svn.apache.org/repos/asf/httpcomponents/httpclient/trunk@1084655 13f79535-47bb-0310-9956-ffa450edef68 |
||
---|---|---|
.. | ||
src | ||
pom.xml |