Uday Subbarayan wrote:
Hi Oleg,
I disagree with you. This 100 status from HTTP Servers are valid response, to indicate to the client to continue sending the body.
You are very welcome to disagree.
RFC 2616, section 10.1
"
10.1 Informational 1xx
This class of status code indicates a _provisional_ response,
...
A client MUST be prepared to accept one or _more_ 1xx status
responses prior to a _regular_ response
...
"
The HTTP 1.1 spec says,
"This interim response is
used to inform the client that the initial part of the request has
been received and has not yet been rejected by the server. The client
SHOULD continue by sending the remainder of the request or, if the
request has already been completed, ignore this response. The server
MUST send a final response after the request has been completed."
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.1.1
A good example is Amzon's S3:
http://docs.amazonwebservices.com/AmazonS3/2006-03-01/
Here client will send the header first and S3 authenticates request based on
header. Then if auth succeeds it will respond with 100 to indicate to the
client to continue with the body OR 417 OT to send the body.
So,
Is it safe to assume that Apache's HTTPClient is NOT supporting this
"Expect:100-Continue" header in HTTP1.1?
You can assume whatever you please. HttpClient is fully RFC 2616
compliant with regards to the expect:continue handshaking.
Oleg
Thanks,
-Uday.
-------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
