MozillaZine

Problem with Firefox and custom 404 error page

Discuss how to use and promote Web standards with the Mozilla Gecko engine.
orogeny
 
Posts: 4
Joined: May 11th, 2010, 7:25 am

Post Posted May 11th, 2010, 7:42 am

My site, http://www.bsc.edu, uses a custom 404 error page. The site uses ColdFusion 9 and is on a Windows Server 2003 R2 server. The error page works in all circumstances in IE, but only works in Firefox when the user has typed in a URL with a .cfm extension. If there is no file extension or a .htm extension, Firefox displays a generic "problem Loading Page" error. Oddly, if one looks at the source code of the generic error page, it is actually the source code for the custom page...Firefox just doesn't display it.

How can I fix this issue?

Examples:
http://www.bsc.edu/about/index.cfm is the correct URL
http://www.bsc.edu/abou/ fails
http://www.bsc.edu/abou/index.htm fails
http://www.bsc.edu/abou/index.cfm fails, but loads the correct error page

All of these links work as intended in IE7 and 8.

DanRaisch
Moderator

User avatar
 
Posts: 117126
Joined: September 23rd, 2004, 8:57 pm
Location: Somewhere on the right coast

Post Posted May 11th, 2010, 9:59 am

Moving to Web Development.

orogeny
 
Posts: 4
Joined: May 11th, 2010, 7:25 am

Post Posted May 11th, 2010, 10:04 am

Sorry about that...my first time on the forums. I should have looked more closely at the categories.

DanRaisch
Moderator

User avatar
 
Posts: 117126
Joined: September 23rd, 2004, 8:57 pm
Location: Somewhere on the right coast

Post Posted May 11th, 2010, 11:32 am

No problem at all.

AlfonsoML
 
Posts: 382
Joined: September 6th, 2006, 1:39 pm

Post Posted May 11th, 2010, 12:50 pm

Your error handler is sending a wrong content-type:
Content-Type: application/octet-stream

If you switch it to text/html it will work.

orogeny
 
Posts: 4
Joined: May 11th, 2010, 7:25 am

Post Posted May 12th, 2010, 12:13 pm

AlfonsoML,

That did it! Thank you so much for your help.

orogeny
 
Posts: 4
Joined: May 11th, 2010, 7:25 am

Post Posted May 12th, 2010, 12:27 pm

If anybody is wondering what caused the issue... when I set up the info for the custom error page in IIS I used a "File" path instead of a "URL" path. This caused the problem with the HTTP header file type.

Return to Web Development / Standards Evangelism


Who is online

Users browsing this forum: No registered users and 2 guests