[ee122] Persistent Connection Hanging
dank at EECS.Berkeley.EDU
Wed Oct 31 00:24:29 PDT 2007
If the file is empty, send the client a 0 byte file. That should work...
----- Original Message -----
From: Jeff Wang <jkwang at berkeley.edu>
Date: Tuesday, October 30, 2007 11:41 pm
Subject: Re: [ee122] Persistent Connection Hanging
> How about when you request a file that is empty and the client is
> The spec doesn't say if we should tack on anything in the entity.
> putting anything in the entity will cause the Safari/Firefox to hang.
> Should we add <space><CRLF><CRLF>, or something else?
> On Oct 30, 2007, at 9:27 PM, vern at cs.berkeley.edu wrote:
> >> When I use Safari, with the keep-alive header, to request a file
> that>> doesn't exist (ie. "/asdfsaf"),
> >> the browser just hangs and keeps on loading.
> >> My server sends a 404 header, but no body.
> >> Apparently, Safari is waiting for more data, but never gets it.
> > RFC 2616 states that a server SHOULD include an entity explaining
> the> problem when returning a 40x status code. Apparently Safari
> > requires this
> > (even though given the SHOULD it should be prepared to deal with its
> > absence).
> > Vern
> ee122 mailing list
> ee122 at mailman.ICSI.Berkeley.EDU
More information about the ee122