hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roland Weber" <ROLWE...@de.ibm.com>
Subject Re: Handling HTTP 1.1 status 100 responses
Date Thu, 17 Jul 2003 08:59:05 GMT
Hello Patrick,

I just had a look into the source code of HttpMethodBase.
The HTTP client deals with 100-continue responses, but
seemingly only when an "Expect:" header has been sent
in the first place. So you might want to add that header.

You can also check for some intermediate proxies that
add an "Expect:" header and do not filter the 100-continue

But this might be an issue for the HTTP client.
RFC 2616 says in chapter 10.1:

A client MUST be prepared to accept one or more 1xx status
responses prior to a regular response, even if the client does
not expect a 100 (Continue) status message. Unexpected 1xx
status responses MAY be ignored by a user agent.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message