Closed
Bug 218293
Opened 23 years ago
Closed 21 years ago
page will not be rendered when called twice (without cleaning the cache)
Categories
(Core :: Networking: Cache, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: sr, Assigned: darin.moz)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1
Wenn calling the example URL the 1st time, the page is rendered correctly. But
when calling the 2nd time (don't forget the parameter) the page will not be
rendered. Instead of that the whole server response will be displayed, starting
with the HTML header. If you clean the cache now, the page will be displayed
correctly the next time.
Reproducible: Always
Steps to Reproduce:
1. Call "https://Server1.4Friendsonly.com/pm/jsp/moz/test.jsp?start=ok" and wait
until "Na bin ich HTML ????" appears.
2. Call "https://Server1.4Friendsonly.com/pm/jsp/moz/test.jsp?start=ok" again
--> page will not be rendered this time
3. Clear cache and repeat from 1.
Actual Results:
Output like this:
HTTP/1.1 200
Date: Thu, 04 Sep 2003 13:39:53 GMT
Server: Apache/1.3.27
Cache-Control: max-age=0
Expires: Thu, 04 Sep 2003 13:39:53 GMT
Keep-Alive: timeout=15, max=97
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html;charset=ISO-8859-1
194
<HTML><HEAD><TITLE>
Paybest
</TITLE>
<META content="text/html; CHARSET=iso-8859-1" http-equiv=Content-Type>
<META content=4friendsonly name=description>
<META content=4friendsonly name=keywords>
<META content=follow name=robots>
<LINK href=/pm/css/pm.css rel=StyleSheet type=text/css>
</head>
<body class=main oncontextmenu="return false">
Na bin ich <b>HTML</b> ????
</BODY>
</HTML>
0
Expected Results:
render the HTML page :)
Comment 1•23 years ago
|
||
I confirmed on Seamonkey too. It's not Mozilla Firebird bug.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030904
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030904 Firebird/0.6.1+
Updated•23 years ago
|
QA Contact: asa
Comment 2•22 years ago
|
||
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031217 Firebird/0.7+
The page was not rendered, even the first time. I always get the HTTP header and
the raw HTML code.
I'm no HTTP expert, but could'nt it be that the server sends two empty lines
before the first line of the HTTP header, thus preventing Mozilla from
interpreting the header ?
Comment 3•22 years ago
|
||
confirming.
Firebird 0.8.0+ (20040120) on XP
the first time it works, but the second time it just displays the html code
Updated•22 years ago
|
Assignee: blake → darin
Component: General → Networking: Cache
Product: Firebird → Browser
QA Contact: cacheqa
Version: unspecified → Trunk
Comment 4•21 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/
Comment 5•21 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•