ivanbessarabov: Chromium has the same settings. Unless someone wants to
work on making that checkbox more discoverable, I think this issue should
be closed.
Another problem with this is that AJAX requests to API's which use header
response codes as a form of communication do not function correctly as
Chrome doesn't give the resulting document to the script.
Ex:
POST http://some.api/users/get
params: username=yourmom&attributes=all
Expected Result:
{"code":404,"message":"yourmom is not a user","result":false,"count":0}
Actual Result:
Google "friendly" page (or nothing at all).
the "turn off suggestions" trick does work.
However, I discovered this after spending around 4 hours today mucking
around in apache configs, thinking that somehow apache must be having
errors, when in actuality, it was simply that a config-file for the web app
was misnamed. Finally found that out when I tried firefox and it gave me
the actual error.
curses...
Comment #24 on issue 1695 by tfar...@chromium.org: Chrome needs option to
turn off "Friendly 404" displays
http://code.google.com/p/chromium/issues/detail?id=1695
(No comment was entered for this change.)
Comment #26 on issue 1695 by tony.chromium: Chrome needs option to turn
The "turn off suggestions" trick does NOT work on Linux 9.0.597 or OSX
9.0.597.
Don't have a Windows box to test on but this bug is definitely still
unresolved.
Also confirmed that this feature is broken on Windows 7 Chrome 8.
For the love of RFC please change this!
In Chrome 10 Linux (the version I'm running) there's an option under "Under
the bonnet" which is called "Use a web service to help resolve navigation
errors" - disabling this causes the web server's own 404/500/etc pages to
be displayed instead of Chrome's - perhaps a nicer explanation of what this
actually does (i.e. next to the option say something like "this will hide
the rather un-standard Chrome error pages")
That option should not exist, neither should the functionality behind it.
mwisnicki is correct. Completely ignoring responses from the server isn't
part of the HTTP protocol.
Reply to sebmayn...@gmail.com
For Windows 7 Chrome 10.0.648.151 disabling "Use a web service to help
resolve navigation errors" has exposed server side error messages as well.
Oh happy day for a viable work around!
I have "Use a web service to help resolve navigation errors" disabled, and
I'm still seeing small error pages being turned into these "helpful" pages.
This is most certainly a step backwards. I was hoping Google dropping
support for oldIE would get rid of the need to support idiosyncratic
behaviours.
14.0.786.0 (Developer Build 88002 Linux)
This is still a problem under linux with Chrome 13.0.782.112.
Please fix it, it's REALLY annoying.