Closed Bug 299453 Opened 20 years ago Closed 19 years ago

In "Page Info" Content-Encoding: type and uncompressed size of a page are missing

Categories

(SeaMonkey :: Page Info, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 121616

People

(Reporter: adefacc, Assigned: db48x)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050604
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050604

When a web page is compressed (i.e. Content-Encoding: gzip), Mozilla shows only
the compressed size (without saying if it is or not compressed), whereas MSIE
5..x, 6.x show only the uncompressed size.
I guess that it would be useful to know both sizes (compressed and uncompressed)
or at least if the page is in a compressed format (gzip, compress, etc.).


Reproducible: Always

Steps to Reproduce:
1. load http://slashdot.org/ (or another site that sends gzipped web pages)
2. open Page Info dialog: View->Page Info (CTRL-I)
3. go to "General" tab and see there is no info about the Content-Encoding:

Actual Results:  
No indication whether the page is or is not compressed.

Expected Results:  
Show the value of Content-Encoding HTTP header and, maybe, the size of
uncompressed page too.
Build: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050702

I can reproduce this bug with the build above.
Duplicate of bug 121616?
Maybe half duplicated, because I explicitly said that Content-Encoding is missing.
I think that the excuse about "NS-4 did not support Content-Encoding (in
Page-Info, etc.) so we don't too", cannot be accepted anymore as far as Mozilla
is approaching version 2.0;  after all Content-Encoding is a property of the
content.
Talking about the expanded size, well, I think it would suffice to add a "Total
Size (bytes)" to the "View Page Source" window.
Content-Encoding being a property of the content means that the "content size" is the compressed size, for what it's worth.

*** This bug has been marked as a duplicate of 121616 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.