248849 - A blank page is produced - even when viewing source and the file cannot be saved to disk. Another browser (lynx) reads page OK.

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Antonomasia]

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

A blank page is produced - even when viewing source and the file cannot be saved
to disk.

Another browser (lynx) reads page OK.

The same goes for other PGP signatures on the site.


Reproducible: Always
Steps to Reproduce:
1.Go to http://www.openssl.org
2.Follow the link where it says the latest d/l is *available*
3.Right Click for save-target-as on chosen links
4.Observe for the PGP sigs that the targets do not get saved.
5.Viewing page source appears blank.
Actual Results:  
blank page

Expected Results:  
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iQCVAwUAQFhAEu6tTP1JpWPZAQHTvgP/Yg+AFejBrtIOsHPGiaJPk0SqO+YtRZul
OCt2eqJUKDh5RrecbcXjuZ6lqvgE1qXXEYELJv+FykvFanFsZqRxY/nKxLZASoG7
nwxq8Z7xTnRoaxp9c+glv88T3APGJQdeTQTwbG2iL9idQJCIAFdzbdlcYHjkUTwr
g2q7Yt/OZ1Q=
=yvqn   
-----END PGP SIGNATURE-----

Comment 1

[Tuomo Valkonen]

It would appear that if there's a gz-component anywhere in the name of the file,
not just as the last extension, firefox thinks the file is gzipped. So, it
thinks these .tar.gz.asc are actually gzipped, while the server correctly
reports text/plain! Brain-damaged.

Comment 2

[Tuomo Valkonen]

After some further examination, it is actually Apache that (in its default
configuration) is absolutely brain damaged, and sets 'Content-Encoding: x-gzip'
for anything with gz _anywhere_ in the name, not just as the last component. So
Mozilla* is probably doing the right thing here and it is Apache that needs to
be fixed. (Strangely, though, .gz.asc appears as a RemoveEncoding example in the
mod_mime documentation, so this is unlikely the happen?)

Comment 3

[Antonomasia]

Bug visible on openssl.org (Apache/1.3.29 shown in header).
More recent 1.3.x not tested.
Bug not present in a default build of Apache 2.0.50 (on Fedora 2).
No record found in apache bugzilla but presumably does not
need reporting there.

Comment 4

[Gervase Markham [:gerv]]

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

[Gervase Markham [:gerv]]

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.