Internet Explorer 8 Turn Off Friendly Error Messages
Contents |
Name Transfers Domain Name Prices Web Forwarding DNS Control Private Registrations Web Applications Web Wiz Forums Web Wiz NewsPad Web Wiz Rich Text Editor Web Wiz CAPTCHA About Us show friendly http error messages chrome About Web Wiz Latest News Why Choose Web Wiz Customer Testimonials Data
Http 500 Internal Server Error Internet Explorer How To Fix
Centre Green Hosting Network Operations Centre Contact Web Wiz Legal Community Knowledgebase Support Forums Web Wiz Blog
Show Friendly Http Error Messages Iis
You are here: Home > Knowledgebase > Classic ASP > HTTP Error Messages Categories Knowledgebase Home Hosting Support Domain Support Control Panel Support Video Tutorials Cloud Server Support Network Tools Classic ASP SEO Website Planning Design a Website Search Related KB's Web Wiz Forums Web Wiz NewsPad Web Wiz CAPTCHA Web Wiz RTE Search Advanced Search Turn Off Friendly HTTP Error Messages in IE (Internet Explorer) A Frequent problem when trying to run Classic ASP applications on your own web space or web server is how do you debug the application if it is not running correctly and only showing a generic error message. All to often in Internet Explorer if the application crashes all you see is a page saying - 'The page cannot be displayed.' then further down the screen you have the generic error 'HTTP 500 - Internal server error'. Well you'll be glad to know there is something you can do to help debug the application and find out what exactly is coursing the application not to run correctly. To do this you need to turn of Internet Explorers, Friendly HTTP Error Messages function, by following the steps below. There instructions work in IE5, IE6, IE7 and IE8. First you need to select 'Tools' from the menu at the top of Internet Explorer. Then from the drop down menu choose 'Internet Options'. Once the 'Internet Options' Dialog box opens you want to choose the 'Advanced' tab. You will then see a list of Advanced functions of Internet Explorer that can be turned on or off by checking the tick boxes. Look down the list for 'Show
WindowsWindows 10 Windows Server 2012 Windows Server 2008 Windows Server 2003 Windows 8 Windows 7 Windows Vista Windows XP Exchange ServerExchange Server 2013 Exchange Server 2010 Exchange Server 2007 Exchange Server 2003 Outlook Unified Communications/Lync SharePoint Virtualization Cloud Systems ManagementSystem Center PowerShell & Scripting Active Directory & Group Policy Mobile Networking Storage TrainingOnline Training IT/Dev Connections Webcasts VIP Library Digital Magazine Archives InfoCentersIT Innovators Mobile Computing Business Now Desktop VDI All About Converged Architecture Advertisement Home > Systems Management > Networking > Informant: Disabling Friendly HTTP Error Messages Informant: Disabling Friendly HTTP Error Messages Feb 4, 2002 Brett Hill | Windows IT Pro https://www.webwiz.co.uk/kb/asp-tutorials/friendly-HTTP-error-messages.htm EMAIL Tweet Comments 2 Advertisement When my Web applications produce an error, the client often sees only the generic HTTP 500 error without any supporting details. Of course, this lack of detail makes troubleshooting difficult. Telling users to disable Show friendly HTTP error messages in Microsoft Internet Explorer (IE) works, but doing so is difficult to manage on a client-by-client basis. What can I do on the server side http://windowsitpro.com/networking/informant-disabling-friendly-http-error-messages to change this IE setting? When the friendly messages feature in IE 5.x or later is enabled, IIS delivers error messages, but IE shows friendly error messages rather than those messages the Web server delivers. When you disable the feature in IE, you're in effect telling IE to show what the server is delivering. (You disable the feature in IE by selecting Tools, Internet Options; clicking the View tab; then clearing the Show friendly HTTP error messages option.) You could deliver to the client a script, object, or executable that changes the appropriate registry setting. However, because doing so involves a high degree of trust by the client to let you make the changes, this process is almost as problematic as walking users through making the change manually. The trick is to get IE to show the error messages without having to modify the client. IE's friendly error messages don't kick in if the number of bytes from the server's error message exceeds a certain threshold (by default, 512 bytes). Thus, if you create a custom message that exceeds 512 bytes, IE will show the custom message, complete with all the error information. (See the Microsoft article "Creating Custom ASP Error Pages" at http://support.microsoft.com/default.aspx?scid=kb;en-us;q224
7 but the theory is the same for IE 8 Steps (6 total) 1 Open Internet Explorer Nice and simple Yes some shameless self promotion of https://community.spiceworks.com/how_to/1085-turn-off-friendly-http-error-messages-in-ie HPS Group - http://oots.be/hpsgroup 2 Open Internet Options You should have a tools https://blogs.msdn.microsoft.com/ieinternals/2010/08/18/friendly-http-error-pages/ button, at the bottom Internet Options 3 The internet options window should popup You should then have some tabs at the top, one says Advanced 4 In the advanced tab You should find a option for "show friendly http error messages" 5 Untick "show friendly http error messages" 6 Hit OK to error messages save the changes Conclusion You should now be done and you can see the real error message of the page. References Unofficial Spiceworks 4 Comments Ghost Chili Lawrie5252 Mar 11, 2010 at 06:17am Nice one Andy, Spiced. I just published one too, Opening ISA Server to being scanned by Spiceworks: http://community.spiceworks.com/how_to/show/1084 Take a look at it and let me know if it looks OK. Pure show friendly http Capsaicin akp982 Mar 11, 2010 at 06:28am Looks good, sent ya a PM :-) Pure Capsaicin Justin.Davison Mar 11, 2010 at 08:17am Nice one Andy, thanks for sharing Tabasco ITMikeNJ Mar 16, 2010 at 09:30am Thanks, Andy. Simple yet elegant. Read these next... Spark: Flaw in Intel chips could make malware attacks more potent Spiceworks Originals Your morning news, a Community wrap up, a lunch recommendation, and the funnies. How do you start a career in IT project management? IT & Tech Careers I have a good amount of project management experience (from the technical side) related to corporate level deployments of software and databases within large companies. But how would I got about going into a carer in IT project management? Configuring and validating SSL certificates This article talks about how to configure both external and internal SSL certificates and give you some hints on how to validate that they are working as expected. © Copyright 2006-2016 Spiceworks Inc. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up with your emai
'14 Friendly HTTP Error Pages ★★★★★★★★★★★★★★★ EricLaw [ex-MSFT]August 18, 20100 Share 0 0 Internet Explorer 5 and later will show a “Friendly” HTTP Error page if the server returns certain HTTP Error status codes with a short message body. The intent is to replace a terse server message like this one: …with a page which may be slightly more helpful to the average user, like this one: Unfortunately, IE's logic isn't smart enough to detect that, say, the response was a tiny HTML page with a META Refresh pointed at a different page, meaning that the META Refresh won't work until you pad the HTML response with enough text to be deemed "non-terse." A common question from web developers is: What makes IE decide to show a friendly error page? The answer is that the server’s response must meet two criteria: The HTTP Status code must be [400, 403, 404, 405, 406, 408, 409, 410, 500, 501, 505] The HTTP Response body’s byte length must be shorter than a threshold value If the server’s response meets both criteria, then IE will show its own Friendly HTTP Error page instead of the server’s terse response. The byte length thresholds are stored in the registry in HKEY_LOCAL_MACHINE under the subkey \SOFTWARE\Microsoft\Internet Explorer\Main\ErrorThresholds. The default threshold is 256 bytes for the response codes [403, 405, 410] and 512 bytes for response codes [400, 404, 406, 408, 409, 500, 501, 505]. If the registry entry is missing for one of the status codes, its threshold defaults to 512 bytes. I wrote a simple script which allows you to test IE’s Friendly HTTP Error pages using Meddler. The next most common question is: How do I prevent IE fr