Closed Bug 157079 Opened 24 years ago Closed 24 years ago

MSI file dumped on the screen

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: kzy37, Assigned: Matti)

Details

MSI binary file (Microsoft installer) are dumped on the screen instead of open 1.0 version on Windows XP
Do you have a URL ? Or do you try to open the msi local ?
Severity: enhancement → normal
Most likely the web server sends it as text/plain or something like that. The offending URL would be most helpful. :)
I've had this before. Yes, the web server was sending them as text/plain. -> Invalid? I say... anyone agree? <offtopic> How do I get permissions for INVALID, DUPE and CHANGESUMMARY? CONFIRM is outlined on one of the bugzilla pages, but not INVALID, DUPE, and the ability to change summaries. </offtopic>
In that case, it's entirely not Mozilla's fault. To save a file that's being sent by the server as text/plain you can right-click on the link and choose 'Save Target As'. I will helpfully render this INVALID. <offtopic>To be able to do the things you mentioned you have to have permission to change any aspect of the bug. Possibly contact Gerv or raise the issue on Mozilla.org's IRC server. I did the latter.</offtopic>
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
this is _NOT_ invalid. (I know why mozilla does this) It's TE if the reporter gives us a URL.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Hmm. Usually when I download a MSI file, it prompts me to save. However, some websites do transmit the encoding as text/plain and cause it to be displayed in plain text. Is there something client-side that's wrong even when the correct MIME-type sent?
Whoops. Scratch out my last comment. Didn't know what I was thinking.
You're right the server, was sending it as text because that’s the default for that server I changed it to “application/octet-stream” and now it acts as in the local file case. Still it doesn’t work as IE because as you say they do not respect the standard. Question: Since a dialog is going to be open in all cases why not to offer the non standard MS approach as a radio button choice? Thanks for solving a problem in my server :) Some MSI Examples: http://apache.secsup.org/dist/httpd/binaries/win32/
>Question: Since a dialog is going to be open in all cases why not to offer the >non standard MS approach as a radio button choice? There is somewhere a bug about that we do this in some cases. (server sends text/plain but extension looks like binary) -> invalid (server error)
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.