Closed
Bug 191713
Opened 22 years ago
Closed 19 years ago
Garbage in some frames of that important site
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: info, Assigned: darin.moz)
References
()
Details
Attachments
(4 files)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030201 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030201 Garbage in some frames of that important german site. At least in the bottom frame. Reproducible: Always Steps to Reproduce: 1. Simply go to that site Expected Results: Properly render the frame
Comment 1•22 years ago
|
||
Worksforme, linux trunk build 2003-02-01-22. ticker in bottom frame renders correctly.
Comment 2•22 years ago
|
||
Wfm Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030130 Ticker renders correctly
Comment 3•22 years ago
|
||
Works for me using solaris 8/sparc nightly 2003020222. The page looks fine and the ticker appears to work properly.
Testing with a day old trunk CVS; Linux: If I allow javascript for the browser, the page looks OK. If I disable javascript, the left menus looks weird, and the ticker at bottom is black. To enable javascript, open Edit->Preferences, click Advanced->Scripts and Plugins and click in box for "Navigator" under "Enable Javascript for" Was that the problem?
Sometimes I see garbage like "Your browser has sent a illegal request" or "Your browser has set an illegal keep-alive-time of 300" or something like that... If I use a proxy everthing works well. But if I do not this morning not all of the frames where loaded. I use http 1.1, pipelining and keep alive. But that settings seems not to affect that problem. The bottom frame with that ticker works now, too. JavaScript seems not to be the problem.
"garbage like "Your browser has sent a illegal request"" Do you see that IN the page? Can you take a screenshot of it when you see it again. Also: Does it happen if you set HTTP Networking to HTTP 1.0 ?
Seems to work now
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 10•21 years ago
|
||
Reporter | ||
Comment 11•21 years ago
|
||
Reporter | ||
Comment 12•21 years ago
|
||
Ok, with Mozilla 1.3 this bug is present again. To show that you only have to connect directly to the internet without proxy and to switch on the "Keep-Alive"-Feature. It seems that the browser sends an incorrect request to that server www.bild.de after an "HTTP/1.1 301 Moved Permanently" comes back. After I checked the response of the following frameset-pages with the help of lynx I see that the following page, which comes with the standard-frameset, has a lot of escape-code in it. Check this link: http://www.bild.t-online.de/BTO/Startseite/StartBuehne,templateId=renderKomplett.html After all I would say, that this is a bug of bild.de. But with the M$-IE you can see the page very well ... The attachements show that behavior.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 13•21 years ago
|
||
Still Wfm, CVS build from today. Perhaps Bug 161464 has something similar to your bug (also there are different error codes)
Comment 14•21 years ago
|
||
This is a networking problem.
Assignee: other → darin
Component: Layout → Networking: HTTP
QA Contact: ian → httpqa
Comment 15•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Assignee | ||
Comment 16•19 years ago
|
||
Marking WORKSFORME. Please reopen this bug if you can still reproduce the problem using Firefox 1.0 or later. Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•