In article <[EMAIL PROTECTED]>, JTK wrote: > Chris Hoess wrote: >> >> In article <[EMAIL PROTECTED]>, JTK wrote: >> > Pratik wrote: >> >> >> >> Nope. Thats just the way websniffer displays it >> >> (http://webtools.mozilla.org/web-sniffer/). Thats not the fault. >> >> >> > >> > >> > Is the cache and specifically the headers written thereto plaintext? If >> > so, I upgrade my WAG to a WAH (wild-ass hypothesis). >> > >> >> CR-LF's are the standard line-end in HTTP transactions and omitting one or >> the otherwould in fact be considered a violation of the standards >> (although we probably play ball with that). They're quite widespread. >> >
[snipped description of the usual CR vs CRLF interoperability problem, etc.] > > So, my WAT (wild-ass theory now) is that the letter "b" will solve this > problem. Before you go promoting this again, your interpretation is tangential to my point. The reason I mentioned the standard is that, AFAIK, all servers (except perhaps for a very few broken ones) transmit CRLF in headers. If there was really a problem with some piece of the cache garbling CRLF, wouldn't this problem affect far more sites? >> Incidentally, are you running any filters on Proxomitron? > > Sure, isn't that kinda the idea? ;-) I'm not at all familiar with the program, I just asked because this triggered the bug I mentioned below. I also recall a Mac program of this nature that doesn't work well with us because it snips out offending tags directly from the data stream (!) and this throws off the timers and makes the parser sulk, or something bizarre. >> There was one >> bug filed by someone experiencing problems similar to yours, but the >> reporter wasn't able to reproduce it on other machines, and it went away >> after a cold install (of Mozilla? Proxomitron?). See bug 100075 for >> details. >> > > Well again, I run IE through the same exact Proxomitron, and view the > exact same CNN, and get two different behaviors. Either two programs > are broken in such a way that the errors cancel each other out, or one > program has a broken cache. > Well, it's the fact that you're only seeing this on CNN that throws me; I'd think other sites would be sending very similar caching HTTP headers. -- Chris Hoess
