Pratik <[EMAIL PROTECTED]> wrote in [EMAIL PROTECTED]">news:[EMAIL PROTECTED], on 21 Dec 2001: > Agreed. But would you please help us figure out who is the culprit? > Just saying Mozilla is doesn't help. If you can answer my > questions, then maybe we can decide its Mozilla but if you don't we > don't have proof that its Mozilla. Its like saying "But this web > page displays fine in IE". Thats no reason to conclude that the web > page is fully standards compliant.
This is my results, with Proximitron: Server: Netscape-Enterprise/4.1CRLF Date: Fri, 21 Dec 2001 17:37:34 GMTCRLF Last-modified: Fri, 21 Dec 2001 17:37:35 GMTCRLF Expires: Fri, 21 Dec 2001 17:38:35 GMTCRLF Cache-control: private,max-age=60CRLF Content-type: text/htmlCRLF Connection: closeCRLF Without proximitron: Server: Netscape-Enterprise/4.1CRLF Date: Fri, 21 Dec 2001 17:38:39 GMTCRLF Last-modified: Fri, 21 Dec 2001 17:38:40 GMTCRLF Expires: Fri, 21 Dec 2001 17:39:40 GMTCRLF Cache-control: private,max-age=60CRLF Content-type: text/htmlCRLF Connection: closeCRLF This is obviously related to some specific combinations of filters, because I have filters enabled, and actually have "Cache-Control: Always cache" and "Expires: Always Cache" enabled in Headers, and "Kill anti- cache" enabled in webpage filters. So I can't reproduce this with or without proximitron... -- ICQ: N/A (temporarily) AIM: FlyersR1 9 email: [EMAIL PROTECTED] _ = m
