RE: [PHP] OT http protocol question & another http question

If you want the connection to close, you can always speak HTTP 1.0 to it. HTTP 1.0 does not have keep alive. -jeremy brand _______________________________________________________________________ GnuPG Fingerprint: 9F5E 95E0 1CC2 E054 84EA 6099 8ACD 9DBA D2C0 5EA9 _ http://www.JeremyBrand.com/Jeremy/Brand/Jeremy_Brand.html for more __ On Tue, 29 Aug 2000, WILSON, Nick wrote: > Date: Tue, 29 Aug 2000 08:23:30 +0930 > From: "WILSON, Nick" <nick.a.wilson@baesystems.com> > To: "'k.bogucki@worldnet.att.net'" <k.bogucki@worldnet.att.net>, php general <php-general@lists.php.net> > Subject: RE: [PHP] OT http protocol question & another http question > > This isn't an answer as that seems to have been taken care of, but say I > have > a web page that fetches another web page, ie does a fsockopen and then > reads in another page. What happens when the header fetched from the other > site > has something along the lines of > > HTTP/1.1 200 OK > Server: Microsoft-IIS/4.0 > Date: Mon, 28 Aug 2000 23:50:05 GMT > Connection: Keep-Alive > Content-Length: 1088 > Content-Type: text/html > Set-Cookie: accept=COOKIES=yes; expires=Tue, 28-Aug-2001 14:00:00 GMT; > domain=.something.com.au; path=/ > Set-Cookie: ASPSESSIONIDGGGGGGBM=LPPHMINAFALDOBMEGGEOBDJN; path=/ > Cache-control: private > > The header Connection Keep-Alive appears to be causing me trouble. Will I > have to > not close the socket and just keep reading and waiting for the site to send > me more > text ? I thought http was open, send request, receive response, close each > time ? > > > -----Original Message----- > > From: Kenneth Bogucki [mailto:k.bogucki@worldnet.att.net] > > Sent: Tuesday, 29 August 2000 4:38 > > To: php general > > Subject: [PHP] OT http protocol question > > > > > > OT re: http protocol > > > > > > As I understand the http protocol, it is a stateless protocol meaning > > once the web page is loaded into the browser, the connection > > to the web > > site is closed. If a user clicks one of the web site links, a > > connection is made and the new page is downloaded and displayed in the > > browser and again the connection is broken > > > > The question is this...if the above is true, then there is no > > difference, in ref: to connection, speed or download time, between > > specifying a link as href=http://thisthat.com/page.php and > > just > > href=page.php3 > > > > right??? > > > > Ken > > > > -- > > PHP General Mailing List (http://www.php.net/) > > To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net > > For additional commands, e-mail: php-general-help@lists.php.net > > To contact the list administrators, e-mail: > > php-list-admin@lists.php.net > > > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net > For additional commands, e-mail: php-general-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net > >