[Prev][Next][Index][Thread]
Re: Netscape and 304 response code bug: Configure the Browser?
Karsten and I went through this very carefully a couple of weeks ago, and
you would seem to be proposing we break the CL-HTTP code.
All HTTP times in HTTP headers are in GMT time. GMT is not effected
by daylight savings time. http::print-gmt-time prints the right GMT time
when daylight savings is in effect or not on Lispm's and the MAC.
So, adding an hour to GMT is not the right thing.
When a locality decides to respect daylight savings time, it is really moving
its time zone by local fiat. Therefore, the problem might be that hosts
have their GMT offsets
set wrong under daylight savings time. On the MAC, there is a switch in
the control panel for
dates and times that needs to be set to daylight savings time.
Why not check and see if setting this switch on MACs solves the looping problem?
I never have this problem on my machines running netscape.
If setting this switch on Netscape works, then we should add a hack to detect
the 304 loop and advise the user to properly configure their computer.
Otherwise, we're looking at a netscape 1.1 bug that we should all complain
about to make sure
it gets fixed in the next release -- which is apparently coming soon.
Let us know if this solves the problem.