Contrary to what Internet Explorer does in most situations, Firefox actually works by the standard and decides things based on the headers that you send, the most important of those being Content-Type. Set it to the actual content type (text/html for HTML, application/msword for Word documents, etcetera) and things magically begin to work as expected. Note that Firefox doesn't embed things like Excel, so that a spreadsheet won't display automatically in the browser window.
The "file extension" should really not make ANY difference. Deciding based on it is bad, and Firefox, to the best of my knowledge, never does that. Internet Explorer does, and by doing so makes things hard for developers. I believe that whether the URL ends in ".cgi" or ".pl" will make absolutely no difference at all for Firefox.
Another thing to look at is Content-Disposition. Set it to inline, not attachment.
| [reply] |
Thanks for your insight. I've grown so used to programming with CGI::Application (which takes care of headers) that I didn't even think about sending headers in this script that doesn't use CGI::App.
Adding print header fixed things. =)
| [reply] |
It seems like it something that is configured with Firefox, try renaming the file to a more acceptable CGI application filename, i.e. some.cgi. This shouldn't affect IE's operation.
| [reply] |