The wireless device should make no difference if the drivers are working
properly, though you could see the odd link failure on long hops.
RFC 1945 says
For response messages, whether or not an entity body is included with
a message is dependent on both the request method and the response
code. All responses to the HEAD request method must not include a
body, even though the presence of entity header fields may lead one
to believe they do. All 1xx (informational), 204 (no content), and
304 (not modified) responses must not include a body. All other
responses must include an entity body or a Content-Length header
field defined with a value of zero (0).
On Tuesday, May 8, 2001, at 01:42 PM, Bill Stoddard wrote:
> Is it reasonable for a client that claims to support HTTP/1.0 to
> -require- a content length header
> on all responses? The client I am working with will discard a response
> if it does not have a
> content-length header. This doesn't sound reasonable to me as the
> server can signal the end of the
> response by closing the connection. Looking for the definitive answer
> before I tell the client
> maker to fix their code.
>
> Humm..... the client is a wireless device which brings up other issues
> that can muddy the picture,
> specifically issues with starting and maintaining TCP connections to
> wireless devices. Looking for
> brain food here :-)
>
> Bill
>
>
Chuck Murcko
Topsail Group
http://www.topsail.org/
