I think what might be happening is: [1] - Active4D shell code closes the connection due to missing “content-length” field in response header
[2] - before the web process gets a chance to expire, the network layer has already accepted (at a lower level) another connection but since it’s closed in the http layer it doesn’t get serviced. [3] - the browser’s left confused. It thinks it connected at the socket level but it’s not getting any response at http level Thats my theory anyway with my very limited knowledge of low level networking protocols :) Peter _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
