Closed Bug 364121 Opened 18 years ago Closed 18 years ago

Content error into direct link downloading files with firefox

Categories

(Tech Evangelism Graveyard :: Dutch, defect, P5)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: tux, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.8.1) Gecko/20061010 Firefox/2.0 if i get a direct link like http://tux.goldchat.nl/Use-mIRC.rar i see the content of it and the file will not download. I try it with internet explore and the file will download Reproducible: Always Steps to Reproduce: 1.install firefox bij default. 2.start firefox bij default profile 3:get a direct download link 4:clicking on direct download link Actual Results: i get a page full with code and the file will not downloading Expected Results: download the file i get this error only in firefox 2.0
it seems that the problem occurs only with that specific link. wfm with other .rar files on other sites. Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a1) Gecko/20061217 Minefield/3.0a1 ID:2006121722 [cairo]
The server responses a wrong content type of "text/plain; charset=UTF-8". This is not a Firefox issue. IE does work because it doesn't look for the MIME type. Instead it decides what to do by evaluating the file extension, which is wrong. This should be fixed by an admin of goldchat.nl.
Status: UNCONFIRMED → NEW
Component: File Handling → Dutch
Ever confirmed: true
Product: Firefox → Tech Evangelism
Assignee: nobody → dutch
OS: Windows XP → All
QA Contact: file.handling → dutch
Hardware: PC → All
Low priority web site. I've been browsing the site for a bit to look for contact information, but I can't seem to find a working link containing such information.
Priority: -- → P5
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.