377318 - When trying to go directly to the above address, I am prompted to open an "application/octet stream"

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[Jon Meredith]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3

Our biz cards have individual web page addresses for our performers (www.partymagic.info/deebest).  In Safari (on my Mac) or in Internet Explorer on my PC, I can key this url in and get right to the page.  In Firefox (the latest build), when I key this in, a small window pops up asking me to "Open deebest" which is an application/octet stream from http://www.partymagic.info  What should Firefox do with this file?"
Any ideas on how to fix this?

Reproducible: Always

Steps to Reproduce:
1.type in the url:  http://www.partymagic.info/deebest
2.Hit Enter
3.
Actual Results:  
a small window pops up asking me to "Open deebest" which is an application/octet stream from http://www.partymagic.info  What should Firefox do with this file?"

Expected Results:  
Taken me directly to the url address.  Like Internet Explorer Does on my PC or Safari does on my Mac.

Please let me know if you can fix this.
eMail:  [e-mail]
cell:  973-809-2932

Comment 1

[Phil Ringnalda (:philor)]

You need to send the correct mime-type, text/html, rather than application/octet-stream. How you go about doing that depends on how you are generating the file - if it's ASP, Google's full of advice on how to properly set mime-type, if it's a static file with no extension, you probably have to set the wildcard mapping to text/html, which is almost certainly a serious security hole and something you shouldn't do, but in any case if you are looking for "how do I change the mime-type that IIS/5.0 sends for a file with no extension" then Google and MSDN are much better bets than b.m.o.

As to things Firefox could change, sniffing things sent as application/octet-stream and treating them as HTML if they look more HTMLish than binaryish, Google's got you covered again for the reasons why it doesn't and won't, with something like http://www.google.com/search?hl=en&q=ie+mime-type+sniffing+security