ericbaze Posted October 14, 2003 Share Posted October 14, 2003 My web site/server is using a custom 404 page written in PHP/HTML (error.php); however, I\'m running into a problem with Internet Explorer. Apparently, there is a default setting for IE where \"Friendly HTTP Error Messages\" is set. This replaces the server\'s error messages with it\'s own version. As this is a default browser setting and 85% of our site viewers are using IE, this setting presents a problem. According to the Microsoft web site (http://www.microsoft.com/window2000...re/iierrcst.htm), any error file larger than 512 bytes should override this setting and display the error page. Our error.php file is much larger than 512 bytes; however, it doesn\'t override the default IE setting. As this posted \"fix\" was probably intended to solve the problem on a Microsoft 2000 server, I appear to be out of luck on our Apache server. I, my IT department, and the support staff of our web host have all researched the issue and been unable to come up with an answer. Also, please note the following: 1) When I tested it, the custom 404 page appeared in multiple Netscape versions and on Safari (which I use at home). 2) With \"friendly error messages\" turned off in IE, my custom 404 page appears as expected. Unfortunately, this option defaults to \"on\" when installing and using IE. 3) When using the default 404 for my server, I achieve the same results as mentioned in #1 and #2. Does anyone have any suggestions on how I can fix this? Obviously under the circumstances, I\'m in-between a rock and a hard place. Any ideas are appreciated! Thanks, Eric Baze, Creative Specialist ConferenceCall.com ebaze@conferencecall.com Quote Link to comment Share on other sites More sharing options...
pauper_i Posted October 15, 2003 Share Posted October 15, 2003 No guarantees on this one, but it may help. Since you are in an intranet environment, grab a copy of the Internet Explorer Administration Kit (IEAK) 6 SP1 and redeploy IE to your users with customised settings. This should allow you to turn the darn bug OFF before you roll it out. Just an idea - overkill perhaps, but I assume you\'re using some form of centralised software deployment so it shouldn\'t be a major problem to do. D Quote Link to comment Share on other sites More sharing options...
ericbaze Posted October 15, 2003 Author Share Posted October 15, 2003 Thanks for your response. Unfortunately, it\'s our main company website (www.conferencecall.com) that\'s causing the problem -- it\'s our current and potential customers who won\'t see the error page with their IE set to defaults. If it were an internal problem, then your solution would be perfect. I don\'t think that there\'s a client-based solution to this, but I could be wrong. Can you think of anything on ther server or within the error page that I could change? Thanks, Eric Quote Link to comment Share on other sites More sharing options...
LAMP Posted October 22, 2003 Share Posted October 22, 2003 You might use header() to try telling your custom page to send a 200 header instead of a 404 ... quick \'n dirty, but might work??? :twisted: Quote Link to comment Share on other sites More sharing options...
ericbaze Posted October 22, 2003 Author Share Posted October 22, 2003 Thanks for your response. How would I implement the header(); command, since this is a 404 error redirect performed by the Apache software rather than the PHP software? Thanks, Eric Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.