385011 - No display in webpage.

Status: RESOLVED DUPLICATE of bug 324363

(Camino Graveyard :: General, defect)

Description

[[e-mail]]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.7) Gecko/20060911 Camino/1.0.3
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.7) Gecko/20060911 Camino/1.0.3

After loading is complete, there is no display whatsoever in the webpage. Used to work fine with Camino. Still works fine with Safari.

Reproducible: Always

Steps to Reproduce:
1.navigate to URL
2.
3.
Actual Results:  
no display

Expected Results:  
display

display

Comment 1

[Stuart Morgan]

In trunk I get "The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression", so this is one of bug 324363, bug 184144, or bug 308858. We'll have to look into it more to figure out which.

Comment 2

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
> rv:1.8.0.7) Gecko/20060911 Camino/1.0.3

By the way, you should upgrade to Camino 1.5 (or 1.0.4 if you're still on Mac OS X 10.2.8).

Comment 3

[Chris Lawson (gone)]

GET / HTTP/1.1
Host: overtheairwaves.com
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en; rv:1.9a6pre) 
Gecko/20070617 Camino/2.0a1pre
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip,deflate
Keep-Alive: 300
Connection: keep-alive
Range: bytes=2465-
If-Range: "a5cba80ce4da69e8aa080c879a94616e34aefc1d"

Packet received at 1182273664.142255
TCP packet from 216.207.4.17:http(80) to 192.168.1.106:52020 (1448 bytes)
ACK
HTTP/1.1 206 Partial Content
Date: Tue, 19 Jun 2007 17:21:04 GMT
Server: Apache/1.3.29 (Unix) mod_fastcgi/2.4.2 PHP/4.4.1 mod_gzip/1.3.26.1a 
FrontPage/5.0.2.2623 mod_ssl/2.8.16 OpenSSL/0.9.7j
Last-Modified: Sun, 17 Jun 2007 16:10:23 GMT
ETag: "a5cba80ce4da69e8aa080c879a94616e34aefc1d"
Accept-Ranges: bytes
Content-Length: 138494
Content-Range: bytes 2465-140958/140959
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html

Might it be a problem that there's no Content-Encoding: header whatsoever, and therefore no way to know that the site is sending gzipped content?

I can make this work after clearing cache, by the way, which sounds really really similar to bug 324363. In the case where it works, a Content-Encoding: header is sent by the server.

cl

Comment 4

[Chris Lawson (gone)]

I'm just going to dupe this over to bug 324363 based on comment 3.