Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

How can I get Chrome to display the HTTP error returned by the server rather than the "friendly" error:

Page could not be loaded The link you specified does not work. This may either be the result of temporary maintenance or an incorrect link.

share|improve this question
up vote 3 down vote accepted

Searching for the text of the error message suggests it may be an EPiServer error page, not a Chrome friendly error message. (There are many matches from with that exact phrase.)

In the version of Chrome I have installed (Chrome 4.0), the friendly error begins with "Oops! This link appears to be broken" and contains alternative links, a Google search box, and the Google logo on the right side. You can turn it on or off by going to the wrench menu → OptionsUnder the hood, then check or clear Show suggestions for navigation errors.

share|improve this answer
I don't see this anymore in current versions (Currently 23) – Peter Walke Dec 28 '12 at 21:08
As of Chrome M40, that setting is under Privacy. You can also use the settings search feature for just "navigation". – poolie Jan 24 '15 at 20:22

This "feature" in Chrome is designed to replace 404 errors by a "friendly" error page for server error pages that do not exceed 512 bytes in size, so were taken by the Chrome developers to be "uninformative". Only from 513 bytes and up is the error page displayed exactly as sent by the server.

The "friendly" 404 error page is also disabled for https.

The problem exists since 2008, when the issue was started in
Issue 1695: Chrome needs option to turn off "Friendly 404" displays,
but was never fixed.

If you control the 404 page returned by the http server, just fill it up with comments so it exceeds 512 bytes, or you can use https. Otherwise, I don't know of a solution.

share|improve this answer
It looks like the nginx developers already know that:… :D – fnkr Jul 14 '14 at 9:40

The friendly errors disappear when using the the developer console open with Ctrl+Shift+I (CMD+Option+I) and then reload the error page to see the error properly.

share|improve this answer

These days (post January 2012) Chrome will only show a friendly error page if the server returns an error page without a body:

Now we only assume error pages without any body at all (content-length: 0) aren't useless to end users.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .