Add a proxy to tell you what is being transfered. I've seen 100 codes before, it's part of a more complex interaction, and I don't know if HttpClient supports this (as I've never used it).
You might be able to force the use of HTTP/1.0, as the spec says from: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html Since HTTP/1.0 did not define any 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions. HTH, sv FYI: http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.2.3 Requirements for HTTP/1.1 clients: - If a client will wait for a 100 (Continue) response before sending the request body, it MUST send an Expect request-header field (section 14.20) with the "100-continue" expectation. - A client MUST NOT send an Expect request-header field (section 14.20) with the "100-continue" expectation if it does not intend to send a request body. On Thu, 20 May 2004, Kedar Panse wrote: > I think you are talking about HttpClient > > Yes I am also getting same thing in the logs. Does anybody know about this? > > Kedar > > Richard Williams wrote: > > > I have a rather simple client using the Post method and I am getting > > the following log message: > > > > Discarding unexpected response: HTTP/1.1 100 Continue > > > > I don't see how this can happen. What can I do to get rid of this > > message. I don't think the server is actually sending the 100. > > > > Richard > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > . > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
