Yes... 1. HTTP GET should never have a "Body", so the CR,LF,CR,LF sequence denotes the end of the request. In other words, Content-Length: 0 is implied for GET.
2. HTTP/1.1 was designed so that the server can receive multiple HTTP requests on the same socket. If we are requiring that the socket close after each request, perhaps we need to have the server be an HTTP/1.0 server. I might try to look into this, later. -- Raul On Mon, Jan 23, 2012 at 9:33 PM, bill lam <[email protected]> wrote: > I do not use IE9 and cannot debug it. A HTTP GET needs not including a > count in its header, so jhs will wait until the remote side close the > socket, if IE9 doesn't, then it will only close by timeout. A possible > solution is to check the presence of two consecutive newline and the absent > of content-length count as a condition to close socket without waiting any > further. > > untested and just a wild guess. > > -- > regards, > ==================================================== > GPG key 1024D/4434BAB3 2008-08-24 > gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
