From: Brian Candler <B.Candler@...>
Date: 2007-05-25T20:59:01+09:00
Subject: Re: Problem with Net/HTTP

On Fri, May 25, 2007 at 08:22:20PM +0900, Peer Allan wrote:
> However, after playing with cURL to get a good look at the whole request 
> I think I may have found the problem.  The failing requests are 
> returning headers that look like this:
> 
> =start
> HTTP/1.1 100 Continue
> 
> HTTP/1.1 200 OK
> Date: Fri, 25 May 2007 11:11:28 GMT
> Server: Apache
> WWW-Authenticate: Basic realm="none"
> Content-Length: 692
> Cache-Control: private
> Content-Type: text/xml
> 
> =end

See RFC 2616 section 8.2.3. The server will only send a 100 Continue if the
client has explicitly asked for it, and therefore the client should be able
to handle it.

Another approach you can do is to build a plain TCP to SSL proxy
(e.g. stunnel), and point your client at stunnel with plain HTTP. This will
allow you to tcpdump the plain connection.

Alternatively, start modifying net/http to show you the raw data sent and
received into openssl, or make an IO proxy object which does that.

Regards,

Brian.