W3C home > Mailing lists > Public > www-lib@w3.org > April to June 2000

Re: POST problem in Libwww-ssl (revisited)

From: Kallweit, Heiner <Heiner.Kallweit@commerzbank.com>
Date: Thu, 15 Jun 2000 16:32:11 +0200
Message-ID: <01EBDB2D6DFDD211A98200805FF50CF901188D03@SV002871>
To: www-lib@w3.org
Hi Sander,

I use POST requests with SSL w/o problems.
What seems strange to me in your former posting is that
your Apache sends a "Connection: close" in the MIME-header.
Normally you should get a "100 Continue" and then send your
POST-body. But you get a "200 OK" status.


> -----Ursprüngliche Nachricht-----
> Von: Sander Alberink [mailto:sander.alberink@cmg.nl]
> Gesendet am: Donnerstag, 15. Juni 2000 15:17
> An: www-lib@w3.org
> Betreff: POST problem in Libwww-ssl (revisited)
> Hi,
> As a follow-up to my message on 13-6 regarding POST on SSL 
> connections, I
> can report that libwww-ssl does not send the body of the POST 
> request, where
> it should have done so. An example program that work fine 
> when used over
> HTTP fails when connecting to a HTTPS server.
> When connecting to a dummy SSL server I see that the body is 
> not sent to the
> server, just the headers. This leads me to believe that the 
> integration of
> libwww-ssl is not complete and it does not send the body of a request.
> Unfortunately, my knowledge of the architecture of libwww is 
> not enough to
> see where the integration is not correct.
> Attached to this mail you will find a test program that 
> clearly demonstrates
> the problem. When the program is used to request the attached 
> perl script on
> a normal HTTP-server, it works fine, but when connecting to a 
> HTTPS-server,
> you will see that the request just hangs (after sending the headers).
> Can anyone shed some light on this?
> --
> The woods are lovely, dark and deep,
> But I have lines to code before I sleep, lines
> to code before I sleep.
Received on Thursday, 15 June 2000 10:33:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:33:52 UTC