274072 - Firefox displays garbage dasBlog default.aspx page

Status: RESOLVED WORKSFORME

(Core :: Networking: HTTP, defect)

Description

[Ayende Rahien]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

When I'm trying to view my blog in dasBlog 1.6 on Firefox 1.0, I get garbage.
When trying the same page on IE, I get the correct result.
Pointing FireFox to default_nocache.aspx works correctly.

You can see for yourself here:
http://www.ayende.com/Blog/default_bad.aspx

The first time you load it it's fine, but do a refresh a time or two and then
the entire page looks like this:
"��v�F�0�[�Vޡ����6A�]��-K��ٖ�e{2I�Wh��@��E��Z�;�_��'9UՍIɤoR�X3�DhTWW"

I tried many encoding, but that doesn't seems to be the problem.
Restarting seem to fix it for the first time or two, but then it display garabge
again

Reproducible: Always
Steps to Reproduce:
1.Go to http://www.ayende.com/Blog/default_bad.aspx
2.Note that the page display correctly (similar to how
http://www.ayende.com/Blog/default.aspx looks)
3.Refresh a couple a time and notice that the whole page is now full of garbage.

Actual Results:  
Firefox displayed garbage the second time I refreshed

Expected Results:  
Should've displayed it correctly like it does this page:
http://www.ayende.com/Blog/default.aspx
IE has no problem reading http://www.ayende.com/Blog/default_bad.aspx and
display it correctly

Comment 1

[Bill Mason]

Not a FF specific bug.

Probably not a Layout bug either, but a place to start.

Comment 2

[Andrew Schultz]

default_bad.aspx loaded badly every time for me with linux trunk 2004120904

default_bad.aspx sent HTTP headers including:

 Cache-Control: public
 Expires: Sat, 11 Dec 2004 06:15:58 GMT
 Vary: *

default.aspx sent HTTP headers including:

 Set-Cookie: ASP.NET_SessionId=deqjtxjn5ckvt455cj44wx45; path=/
 Cache-Control: private

other headers were the same between the two URLs.
==> http

Comment 3

[Phil Ringnalda (:philor)]

Reporter, can you tell us anything about the content-encoding setup on the
server? The one time I got a good result, it was (from Live HTTP Headers):

GET /Blog/default_bad.aspx HTTP/1.1
Host: www.ayende.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0
Accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: ASP.NET_SessionId=vbelyt5541j3u3455dkc2145

HTTP/1.x 200 OK
Server: Microsoft-IIS/5.0
Date: Sat, 11 Dec 2004 05:23:20 GMT
X-Powered-By: ASP.NET
X-AspNet-Version: 1.1.4322
Content-Encoding: deflate
X-Pingback: http://www.ayende.com/Blog/pingback.aspx
Cache-Control: public
Expires: Sat, 11 Dec 2004 06:15:58 GMT
Vary: *
Content-Type: text/html; charset=utf-8
Content-Length: 21374

while the response for every bad load includes:

Content-Length: 21384

Is something (correctly) changing that would add those extra 10 bytes between
one load and the next?

Comment 4

[Ayende Rahien]

Nothing should change between one invocation and the next. The encoding on the
server is either English or Hebrew

Comment 5

[Phil Ringnalda (:philor)]

Wups, lost track of this bug. The "Content-Encoding" header isn't character
encoding, like utf-8 or iso-8859-8, it's something that was done to the entire
response body before sending it, usually compression. In this case, your server
was applying the "deflate" encoding, but it was apparently getting it wrong, and
producing a different size when it got it wrong than when it got it right.
However, it looks like now default-bad.aspx is being sent with gzip rather than
deflate, and is surviving that just fine, which means there's nothing left we
can do here, so I'm resolving the bug worksforme.