Closed Bug 93984 Opened 24 years ago Closed 23 years ago

File corruption when downloading Windows executable via https

Categories

(Core :: Networking: HTTP, defect, P1)

x86
Windows 2000
defect

Tracking

()

VERIFIED WORKSFORME
mozilla0.9.8

People

(Reporter: brianclark44, Assigned: darin.moz)

References

()

Details

Attachments

(1 file)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.3) Gecko/20010801 BuildID: 2001080110 For some reason, I was unable to download an uncorrputed 29MB file from the above website. You have to have a password to login, but I thought you could use the URL to figure out what webserver they are running, if that mattered here. When I downloaded the file with Mozilla 0.9.3 on Win2k, the 29MB file turned into a 40+MB file, and was corrupted. When downloading with IE 5.5, it was correctly sized as 29MB, and was not corrupted. Reproducible: Always Steps to Reproduce: 1.Login to website (you won't be able to, as it requires a password) 2.Navigate to the SAPGUI Frontend patch download directory 3.Download a file.
is the file compressed in any way?
I believe that the file is a winzip self-extracting executable.
Reporter: Is this still a problem with 0.9.4 or later ? (I can't test this becuase my connection is slow [ISDN])
I just checked with Windows build 2001100503 and this is still a problem. Same as before, a file that was supposed to be 1.7MB turned into a 2.5MB file upon download, and was corrupted so that it was no longer executable on my Win2k macine. This time the download was from https://www010.sap-ag.de. Again, I believe that the server that I am downloading this from is Microsoft IIS running on Win2k.
Reporter: Can you give us the download URL of that file ?
Unfortunately, you need an SAP userid to get at this. SAP only gives userid's to their customers and employees. If you have one, then try downloading this file. It is the Windows installer for their Java Download manager. https://www001.sap-ag.de/~sapidb/002006825000000233132001/install.exe
brian: can you please capture a HTTP log using a nightly build. here's how: from a DOS prompt, type the following: set NSPR_LOG_MODULES=nsHttp:5 set NSPR_LOG_FILE=http.log next, cd to the directory containing the mozilla executable, and run it from the DOS prompt. attach the log file to this bug report, and i should be able to make a better guess at what the problem might be. thx!
Attachment #52675 - Attachment mime type: text/zip → application/x-zip-compressed
No dupes found. Marking NEW. -> File Handling?
Assignee: neeti → darin
Status: UNCONFIRMED → NEW
Ever confirmed: true
-> 0.9.8 (thanks for generating the log file)
Priority: -- → P1
Target Milestone: --- → mozilla0.9.8
here's the interesting part of the http log file: 1556[b470c8]: http response [ 1556[b470c8]: HTTP/1.1 200 OK 1556[b470c8]: Server: Microsoft-IIS/5.0 1556[b470c8]: Connection: close 1556[b470c8]: Content-Location: https://www001.sap-ag.de/scripts/httpstat.htm 1556[b470c8]: Date: Tue, 09 Oct 2001 04:48:06 GMT 1556[b470c8]: Content-Type: application/octet-stream 1556[b470c8]: Accept-Ranges: bytes 1556[b470c8]: Last-Modified: Sun, 16 Sep 2001 10:01:59 GMT 1556[b470c8]: Etag: "7acdf39f963ec11:8b4" 1556[b470c8]: Content-Encoding: gzip 1556[b470c8]: Transfer-Encoding: chunked 1556[b470c8]: Expires: Wed, 01 Jan 1997 12:00:00 GMT 1556[b470c8]: Cache-Control: max-age=86400 1556[b470c8]: Vary: Accept-Encoding 1556[b470c8]: ] notice that the Content-Type is application/octet-stream and also notice that the Content-Encoding is gzip. in this case, mozilla will save the message body in gzip'd format. this probably explains why the reporter was unable to use the download file. it was not in the expected format. reporter: can you try downloading the file again, and save it with a name similar to file.gz. then try opening the file using winzip. if i'm right, winzip will show you the file you want.
I tried downloading this again, with Mozilla 0.9.6, and it works fine. I didn't have to change the file extension to .gz, as you suggested. Perhaps this was a problem with SAP's web server configuration, and nothing to do with Mozilla? Anyway, I tried it with Netscape 6.2.1 (Mozilla 0.9.4+) and it also worked fine, so I suspect it was something done on the web server side, rather than the browser side.
marking WORKSFORME
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
verified wfm
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: