247086 - download CRL into file (from HTTPS site) may result in an invalid CRL

Status: RESOLVED EXPIRED

(SeaMonkey :: Download & File Handling, defect)

Description

[Götz Babin-Eell]

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

Mozilla seems not to be able to download some CRLs to file.

Downloading a CRL into a file 
https://www.trustcenter.de/fcgi-bin/CRL.cgi/TC_Class2.crl?Page=GetCrl&crl=3
will result in a file that contains data from the certificate but that
is definitively not an CRL.
(This may change the moment the now active CRL is replaced by another one)

Importing the CRL into mozilla heppens without an error.

If at the end of the download is an small delay, the downloaded CRL is broken.


Reproducible: Always
Steps to Reproduce:
1. Download CRL into file from
   https://www.trustcenter.de/fcgi-bin/CRL.cgi/TC_Class2.crl?Page=GetCrl&crl=3

Actual Results:  
the CRL contains invalid data.


Expected Results:  
I downloaded the CRL with curl, wget and Netscape 4.73 (M$IE downloads OK, too)
I got the correct CRL (230401 bytes long):
(CRL number 2344, from Jun 16 06:09:19 2004 GMT until Jun 23 06:09:19 2004 GMT)

The broken one has a length of 452874 bytes)



CRLs downloaded available at request.

Comment 1

[Götz Babin-Eell]

Attachment: the broken CRL downloaded with mozilla (compressed (bzip2 --best)to allow upload)

Comment 2

[Götz Babin-Eell]

Attachment: the correct CRL (compressed for upload)

Comment 3

[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 4

[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.