Closed
Bug 263400
Opened 20 years ago
Closed 20 years ago
does not render 'odd' web pages with custom extensions
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jim, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 we use custom extensions for our templates (we wrote the actual web server that does the template evaluation), this extension is .HTT . In IE and Opera, the browser requests the page from the server and it sends back a normall HTML page. But in FireFox 1.0Preview when that page is requested, it pops up a dialog asking me what external program to use to handle that file type, then sends the un-expanded version of the file. I saw no way to instruct FireFox to ingnore this file and simply request it from the server. Reproducible: Always Steps to Reproduce: 1. Unfortunately you can not reproduce the problem exactly as I am because you don't have the same web server. But If you simply rename a normal HTM file to HTT you should see the same behavior when you try and load that file. 2. 3. Actual Results: got a dialog box wanting me to choose an external application to handle the HTT file type. Expected Results: make a request of the server to send the file over and then render it on the browser not send it to a remote program. I did try and associate the HTT file extension with FireFox but when I tried to load the web page FireFox went into a loop opening new windows over and over again. I had to kill the process in the Task Manager.
Comment 1•20 years ago
|
||
You're probably not serving the file as text/html, so Firefox won't display it as HTML. Check your server MIME settings.
Comment 2•20 years ago
|
||
assuming that fixed it (no response), ->WFM feel free to reopen if it's continous to be a problem (not caused by your server)
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•