W3C home > Mailing lists > Public > www-lib@w3.org > July to September 1999

HTTP Question

From: Allen Comer <allen.comer@entropic.com>
Date: Tue, 20 Jul 1999 16:48:46 -0400
Message-ID: <F18326290662D211921B00105A2987678253@sheik.entropic.com>
To: "'www-lib@w3.org'" <www-lib@w3.org>
Hi all,

I'm using libwww to in an application that involves pulling multiple
pages from a single site.  If I use the HTTP 1.1 default, the server
responds in the following manner:

HTTP/1.1 200 OK
Server: Microsoft-IIS/4.0
Date: Tue, 20 Jul 1999 19:27:52 GMT
Connection: close
HTTP/1.0 200 OK
Content-type: text/html
Date: Tue, 20 Jul 1999 19:27:52 GMT
Expires: Tue, 20 Jul 1999 19:27:52 GMT
Cache-control: private
Set-Cookie:
User1=2583D742DDAC83B91CEB4C53A66AAE414DC1BC4554E98B5DF4D408; path=/;
Set-Cookie: User2=3515602B767FD9DD; path=/;

This seems strange since there are two "HTTP/1.x 200 OK" header lines
and two "Date:" header lines within the same response.  THe problem in
the above situation is that the cookies expire at the end of the session
and the server closing the connection renders them useless for a
subsequent page grab.  So, I then set my application to use HTTP 1.0 the
server sends the same response but without the "Connection: close"
header.  My application, however, hangs after the first request.  I,
more or less, do the following:

issue request 1
start event loop
get cookies
delete request 1
stop event loop
issue request 2 with cookies
start new event loop
 
However, I can't get to the second request.  So, regardless of which
HTTP version I use, I'm stuck.  I explicitly send a "Keep-Alive" in my
request header under 1.1.  Anyone have  ideas?  

Thanks,

allen
Received on Tuesday, 20 July 1999 16:45:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:15:17 UTC