[dev] [cvs] commit: framework/Browser Browser.php
Michael M Slusarz
slusarz at mail.curecanti.org
Sat Dec 10 18:33:03 PST 2005
Quoting "Kevin M. Myer" <kevin_myer at iu13.org>:
> Quoting Michael M Slusarz <slusarz at curecanti.org>:
>
>> slusarz 2005-12-10 17:34:46 PST
>>
>> Modified files:
>> Browser Browser.php
>> Log:
>> I can't remember why we disabled Content-length for HTTP 1.1 servers. But
>> the RFC (and browsers) expect this information. According to RFC
>> 2616 [4.4(3)],
>> the only time you would not send a Content-Length header is if the
>> Content-Transfer-Encoding header is sent. Since we control the
>> headers being
>> output in downloadHeaders(), and we don't send this header, we should be
>> sending the Content-Length header.
>
> Apparently to fix broken browser behavior..
>
> http://marc.theaimsgroup.com/?l=imp&m=104354282712696&w=2
Thanks... my search strings weren't finding anything.
If this is the reason... 2003 would have been before Mozilla 1.0 was
released. So it doesn't make sense to keep suppressing Content-Length
as it seems to work fine on Mozilla now.
michael
_______________________________________
Michael Slusarz [slusarz at curecanti.org]
More information about the dev
mailing list