Hi Darin,
thanks for your response.
Darin Fisher wrote:
..
> Interesting... can you send me a sample URL that demonstrates this problem.
I think, others have already provided examples for that.
> Ok... please use about:cache to inspect the cached content for that
> ticker URL... when you pull up about:cache, it is possible to click on
> the anchor tag for a particular entry and get HTTP headers. I'd really
> appreciate it if you could send me those headers along with the other
> info in about:cache for that URL.
Certainly. (Sorry for the delay, but I'm in a very different timezone
;-)
The ticker URL is http://de.news.yahoo.com/3/, its about:cache entry:
Key: http://de.news.yahoo.com/3/
Client: HTTP
Data size: 26649 Bytes
Fetch count: 1
Last Fetched: Fri 16 Mar 2001 10:21:21 AM CET
Last Modified: Fri 16 Mar 2001 10:21:22 AM CET
Last Validated: Fri 16 Mar 2001 10:21:21 AM CET
Expires: Sat 18 Aug 2035 03:57:13 PM CEST
Stream based: TRUE
... which is strange, as NS 4.76's about:cache entry of the same URL is:
URL: http://de.news.yahoo.com/3/
Content Length: 26649
Content type: text/html
Local filename: 01/cache3AB1DB21007431B
Last Modified: No date sent
Expires: No expiration date sent
Maybe Mozilla is dreaming up the ultra-long expiry time? ;-)
Anyway, if I click on Mozilla about:cache entry key anchor, I get:
key:http://de.news.yahoo.com/3/
request-time: Tue 04 Jun 2019 04:52:54 AM CEST
response-time: Fri 16 Mar 2001 10:21:21 AM CET
http-headers:
HTTP/1.0 200 OK
date: Fri, 16 Mar 2001 09:20:25 GMT
cache-control: private
content-type: text/html
Uhh, the request time surely looks strange.
Do you need any more info? (... but anyway you wouldn't get a response
before Monday :-)
Cheers, Nils
PS. this is with build 2001031609 UTC main trunk. I haven't checked out
your bug fixes on the other branch. I do that now.
