On 12/21/01 02:22 PM, JTK wrote: > > ------------------------------------------------------------------------ > > Subject: > > Re: It's December 14th again! > From: > > JTK <[EMAIL PROTECTED]> > Date: > > Fri, 21 Dec 2001 13:22:53 -0600 > > Newsgroups: > > netscape.public.mozilla.general > > > Not snipping headers to illustrate yet another major defect in Mozilla > (just so nobody thinks I'm "lying" (or did I quadruple-space these > myself?)). Conditions to recreate: hit the reply button.
Known and filed bug. Hopefully it will get fixed soon. > > Pratik wrote: > > >>------------------------------------------------------------------------ >> >>Subject: >> >>Re: It's December 14th again! >>From: >> >>Pratik <[EMAIL PROTECTED]> >>Date: >> >>Fri, 21 Dec 2001 11:21:58 -0500 >> >>Newsgroups: >> >>netscape.public.mozilla.general >> >>Path: >> >>secnews.netscape.com!not-for-mail >>Newsgroups: >> >>netscape.public.mozilla.general >>Organization: >> >>Another Netscape Collabra Server User >>Lines: >> >>65 >>Message-ID: >> >><[EMAIL PROTECTED]> >>References: >> >><[EMAIL PROTECTED]> >><[EMAIL PROTECTED]> >><[EMAIL PROTECTED]> >><[EMAIL PROTECTED]> >><[EMAIL PROTECTED]> >><[EMAIL PROTECTED]> <[EMAIL PROTECTED]> >><[EMAIL PROTECTED]> >><[EMAIL PROTECTED]> >><[EMAIL PROTECTED]> <[EMAIL PROTECTED]> >>NNTP-Posting-Host: >> >>65.117.135.98 >>Mime-Version: >> >>1.0 >>Content-Type: >> >>text/plain; charset=us-ascii; format=flowed >>Content-Transfer-Encoding: >> >>7bit >>User-Agent: >> >>Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7+) Gecko/20011220 >>X-Accept-Language: >> >>en-us >>Xref: >> >>secnews.netscape.com netscape.public.mozilla.general:37516 >> >> >>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. >> > > > No, then it would be [snip]. Okay will use snip from now on. > >>If what I suggested didn't work, then I would have gone back and >>paid more attention to what you said. >> >> > > > Well now that sombody else has entered a bug on this, feel free to do > so. Hell, feel free to add it to the bug if that's possible. > Yes but the question is are the two bugs the same? The page mentioned were different. I've looked at the headers and the headers are different. The conditions in which the bugs were produced are different. The big difference being Proxomitron. If you can confirm that the bug happens with Proxomitron shut down, then I agree you might be seeing the same bug. > >>>>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? >> >> > > Isn't that AOL's job? I don't work for AOL. And neither do I. I was just trying to home in on the bug. > > >>>>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* don't have the problem sir, AOL does. I've brought it to your > attention in the vain hope that it might actually get fixed someday. If you would help localize the bug, the problem would get fixed. > >>I tried helping you in tracking this down. The least you could >>do is confirm what people are suspecting. >> > > Actually people (I hope not you) are suspecting that I'm lying. I don't but for the life of me I can't figure out why you won't post *your* headers and why you won't try doing what the reporter in bug 100075 did. It would have taken you less time to write this mail then to try those things. > >>That its the >>Mozilla/Proxomitron interaction thats the problem. Can't you confirm >>that? If you can confirm it, people can investigate. >> >> > > Like I said, AOL can certainly investigate this themselves if they want > to. If they don't want to, I certainly can't force them to. No you can't but by giving exact instructions to reproduce, you can help. By trying out various permutations/combinations suggested in this thread, you can help localise the bug and get it fixed. > >>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. >> >> > > > Alright, tell you what. You stop calling *my* suspicions "crap" and > I'll do this for you and AOL. Gratis. Done. No more "crap" from me. Now will you post your headers, try out what bug 100075 says and tell us what happens? > >>>My statement still stands: IE works fine, Mozilla shows me old CNN. >>>That's a freebie. You're welcome. >>> >> >> >>Agreed. >> > > > Agreed what? You agree that there's a problem? What do you need me and > my "crap" for then? I agree with you that there'saproblem on your machine. Now we just need to get to the root of it. > >>But would you please help us figure out who is the culprit? Just >>saying Mozilla is doesn't help. >> > > You ostensibly didn't know about it before. Now you do. It's therefore > helped. Right now I suspect there's a problem with Mozilla/Proxomitron interaction. Just need to figure out exactly what is going wrong. > >>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. >> >> > > > You saw the headers that somebody posted, right? (Or was that you > yourself that posted them?) Are they OK or not? yes they are okay but that person was*not* seeing your bug with his Proxomitron config. But you are. Hence we need to se *your* headers. > >>Did you try Opera to see if that works well? >> >> > > > No. But here, I'll try NC4.78... > > ...it's fine, through Proxomitron. But guess what - Mozilla again shows > yesterday's CNN. I'll even post a screenshot for you. I'll wait for the screenshot. Pratik.
