Richner Simon wrote: > I'm not too familiar with the HTTP-specifications, but the problem seems > to be, that if a message is larger than the MSS, specified by the client, > the server is expected to set the Content-Length Option.
Exerpt from RFC 1945 (HTTP 1.0 specification), chapter 10.4 "Content-Length": "Applications should use this field to indicate the size of the Entity-Body to be transferred, regardless of the media type of the entity. A valid Content-Length field value is required on all HTTP/1.0 request messages containing an entity body." So for requests (POST), Content-Length is needed, while for responses (GET response, in your case), it is not required (note the word "should"). The browser should receive all data up to the FIN - the server sends all data and closes the connection at the end of the file. Content-Length can help, but I wouldn't expect an HTTP/1.0-compliant browser to fail like you observed... Simon -- GMX DSL SOMMER-SPECIAL: Surf & Phone Flat 16.000 für nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
