Firefox won't display default page

[ccs]

A number of customer's have started complaining to me that their web sites won't work with FireFox any longer (seems like this began about 3-5 weeks ago).

Pages render just fine in IE., Opera, and Safari, but FireFox insists on wanting to download the default page instead of displaying it.

I've tested this on a number of web sites hosted on this server and they all display the same behavior.

The main site is: www.ccsolutions.net

Any ideas?

[TRUSTAbyss]

The Content-Type header is set to "application/octet-stream". Did you mess around with the MIME Types? Also, if you right click the web page in I.E. and click Properties, the Type is set to File. It's your MIME Types causing it. Make sure you have "htm" and "html" set as "text/html" in the MIME Types configuration.

[ccs]

Ok, found the server settings for mime types. never saw this before.

...found an old backup config file for Abyss and copied the mime types that were defined there. Firefox now seems happy to play with my customer's web sites again.

Thanks for pointing me in the right direction!

[TRUSTAbyss]

There might be a bug in Abyss Web Server. You should have MIME Types defined. What did you do before this happened?

[ccs]

To the best of my knowledge, all I did in the last 4-6 weeks or so, was install the newest version. Could have happened then, I really don't know as this is the first time I've had this reported to me. I don't use Firefox so I didn't see it myself until today.

Do you know what the settings should be? At this point, I really don't care why, I need to get it fixed (this is a commercial server, not a personal site). If I can't get the default settings (which must have worked before) then I'll have to move these sites to a different server until such time that I can find out what to put in the config file.

Thanks!

[TRUSTAbyss]

What version did you upgrade from? If you send your abyss.conf file to Aprelium, they might be able to help you better.

[ccs]

Not sure what the exact version numbers are, but when a new one is released, I install it immediately on a test server which is a mirror of the primary and using DNS Round-robin it gets a pretty good work out. Unless I spot some glaring bug, I upgrade the production server about a week later. So this one is running the most current, upgraded from the release version just prior to it.

In any case, read through a backup config file and restored the mime settings which has fixed the issue.

I greatly appreciate your help!

[TRUSTAbyss]

I was just about to ask you if you kept a backup. If you encounter the problem again, try and reproduce it. I haven't encountered any of these problems since upgrading just so you know.

I'm glad the problem is now fixed.