Ie User Friendly Error Messages
'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 show friendly http error messages chrome the server returns certain HTTP Error status codes with a short message body. show friendly http error messages iis The intent is to replace a terse server message like this one: …with a page which may be slightly more 500 internal server error 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 from showing the friendly error page? If a user wants to prevent display of all Friendly HTTP Error pages, they can untick an option in the Internet Control Panel's Advanced tab, then restart IE. Of course, only the Friendly HTTP Error pages can be disabled in this way; other Friendly Error pages (like the DNS Lookup error or TCP/IP Connection failure page) cannot be disabled because IE has no other content
communication with an HTTP server. Friendly error messages are appropriate for the end user. However, they https://blogs.msdn.microsoft.com/ieinternals/2010/08/18/friendly-http-error-pages/ can prevent administrators from seeing the literal HTTP error codes and explanations, which makes troubleshooting difficult, if not impossible. During the discovery phase of troubleshooting, https://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/2fb45f42-eaa8-4de5-a17d-5932eabeaa89.mspx you can gather and record the HTTP errors that have occurred if you have disabled friendly messages.To disable friendly HTTP error messages in Internet Explorer1.On the Tools menu in Internet Explorer, click Internet Options.2.Click the Advanced tab.3.In the list of options under Browsing, clear the Show friendly HTTP error messages check box.4.Click Apply, and then click OK.Top of pageManage Your Profile© 2016 Microsoft Corporation. All rights reserved.Contact Us |Terms of Use |Trademarks |Privacy & Cookies
messages are as bad as they can be even forgetting to use the 404 status code in the HTTP header. It is high time http://www.xmlplease.com/error404 to reconsider if the job is better left to an improved default 404 provided by web servers where it naturally belongs. 1. Design for error 2. Hypertext Transfer Protocol 3. Code 404 must be returned 4. Default 404 in web servers 5. Friendly HTTP error messages in Internet Explorer 6. Microsoft's "custom" and "friendly" 404 7. The friendly 404 in IE7 beta 8. The short and error messages the expanded error message 9. Brain storm for a good 40410. Google's 404 error message11. Jakob Nielsen's 404 error message12. IBM's 404 error message13. PHP's 404 error message14. Microsoft's 404 error message15. Yahoo's 404 error message16. Ebay's 404 error message17. Wikipedia's 404 error message18. W3C's 404 error message19. Evolt's 404 error message20. Alistapart's 404 error message21. Amazon's 404 error show friendly http message22. XmlPlease's 404 error message23. Common errors in 404 messages24. Don't make smart error messages25. Resources26. Conclusion27. Appendix27.1 Revision history27.1.1 2007-01-2927.1.2 2006-07-2127.1.3 2006-07-1727.1.4 2003-05-171. Design for errorWhen you have used the web for some time, you know that an URL does not always lead you to what you expected and that links can be broken. Just like telephone numbers. No big deal. You don't need to hear "we are sorry", or to be presented for a long list of possible causes or a similar long list of suggestions for how to proceed.We want to recognize that a "404 Not Found" has happened as fast as possible. It is not necessarily better to make a less technical message. It will probably be longer and also less clear at a glance. We want to correct the typo or mis-spelling in the address line of the browser right away, if that is the problem, or to go to the homepage of the URL not found in a split second, and to proceed from there.The pr