On 12/21/01 08:08 AM, JTK wrote: >> <snipping all the crap> >> > > > Crap huh? We back to "it's all a dream" now?
Crap because I was more interested in the interaction than stuff about CRLF. If what I suggested didn't work, then I would have gone back and paid more attention to what you said. >>The question still stands. Did you try out what the bug suggests? Yes or >>No? >> > > No. Why won't you even confirm that its the interaction thats causing the problem and not Mozilla by itself? > >>And did that solve your problem? Yes or No? >> >> > > N/A. > > Are you telling me that AOL doesn't have the paid resources to install > Proxomitron, pull up CNN, wait a few days, then pull it up again? No I'm saying that if you have a problem and people ask you to try something to see if it helps, you should try and let them know the result. I tried helping you in tracking this down. The least you could do is confirm what people are suspecting. That its the Mozilla/Proxomitron interaction thats the problem. Can't you confirm that? If you can confirm it, people can investigate. More things you could try. With Proxomitron on in all its glory, go to http://webtools.mozilla.org/web-sniffer/ Type in www.cnn.com, click on verbose mode, hit the submit button and post the HTTP header that you see. > > My statement still stands: IE works fine, Mozilla shows me old CNN. > That's a freebie. You're welcome. 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. Did you try Opera to see if that works well? Pratik.
