> explicitly define the Content-Length up-front (clients then usually don't like it if you send too little and servers don't like it if you send too much) We h

> explicitly define the Content-Length up-front (clients then usually don't like it if you send too little and servers don't like it if you send too much) We had a small router/firewall thing at a previous company that had a web interface, but for some reason its Content-Length header had an off-by-one error. IIRC Chrome handled this okay (once the connection was closed it would display the content) while Firefox would hang waiting for that one extra byte that never came.