[dev] Re: [cvs] commit: horde/lib Horde.php

[Michael M Slusarz]

Quoting Chuck Hagenbuch <chuck at horde.org>:

| Quoting Michael M Slusarz <slusarz at bigworm.colorado.edu>:
| 
| > I found the location of this problem too, BTW.  It is in
| > horde/javascript.php - for whatever reason Mozilla does not like the
| > Content-Length header.  If you remove this line, the pages load fine
| > (I've noticed similar behavior when downloading files with Mozilla - it
| > takes 10x as long to download using Mozilla as IE.  I'm assuming this
| is
| > because of this problem also).
| 
| Okay, I've removed the Content-Length: header from javascript.php for
| now.
| Does this help folks? Does it cause any problems? Should we not send it
| in
| other places, as well?
| 
| -chuck

I found this note

-----

benc: for example, consider CGI output.  HTTP/1.1 servers typically use a
chunked transfer encoding with CGI output, hence they don't need to worry 
about
specifying a Content-Length.  HTTP/1.0, however, does not define chunked
encoding, and HTTP/1.0 servers often don't enforce a valid Content-Length
header.  The HTTP/1.1 spec is very specific about this unfortunate 
circumstance.

but, it should be noted that we also allow HTTP/1.1 servers to lie about the
Content-Length, provided the connection is not persistent.  this is 
consistent
with IE's behavior.

-----

at http://bugzilla.mozilla.org/show_bug.cgi?id=95466

Thus - maybe we don't need Content-Length for HTTP/1.1 servers?  I've added 
a check in Server:: for the HTTP Protocol, and Content-Length will not be 
sent anymore in a download request if we are using 1.1.  Let's see if this 
works any better...

michael

______________________________________________
Michael Slusarz [slusarz at bigworm.colorado.edu]
The University of Colorado at Boulder