Closed
Bug 82319
Opened 24 years ago
Closed 24 years ago
gzip transfer encoded pages are saved in gzip format
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: petchema, Assigned: neeti)
References
()
Details
1) Load some page with Transfer-Encoding: gzip method
2) Save it with "File/Save As" menu
3) The file created contains the page, but gzipped
(untested with other encoding formats, it could be a more general problem)
dup
*** This bug has been marked as a duplicate of 35956 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
oops... you say it remains gzipped - this isn't a dup.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
This is *not* the same bug as #35956.
Also, this was tested with Mozilla 0.9 (Debian unstable), Apache 1.3.9 +
mod_gzip 1.3.19.1a.
Comment 5•24 years ago
|
||
http://www.moviecovers.com/ does not support Transfer-Encoding (Mozilla doesn't
either). It sends *Content-Encoding*, which indicates that the resource should
be saved in encoded format. This bug is the opposite to bug 35956. If we fix
35956 (seems to be broken again in some recent nightlies), we cannot fix this
one. In both cases the very same Content-Encoding header is used.
I mark this INVALID. See bug 35956 and bug 51852 for further arguments.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•