Re: Re: why do we not set http 500 for errors when the display_error is enabled

On 25.06.2014 17:39, Rowan Collins wrote: > Andrea Faulds wrote (on 25/06/2014): >> On 25 Jun 2014, at 15:32, Ferenc Kovacs <tyra3l@gmail.com> wrote: >> >>> I see. I assume this is related to >>> http://support.microsoft.com/kb/294807 >>> where by default IE shows pretty but generic message for non-2xx >>> messages >>> if the response content length is less than or equal to a specific >>> threshold(512 bytes for 500 errors for example). >>> I don't think that it was a good idea to patch our error handling for >>> the >>> sake of an usability feature only present in one browser. >> Don’t other browsers do this as well? I believe Chrome and Firefox do, >> at least for 404 errors. > > Firefox and Chrome only show the default message if the response length > is ZERO bytes. Even the 26-byte response generated by empty content > going through gzip buffering appears to be enough for them both to show > the "real" output (in that case, a blank page). > > So it really is just IE that has this notion of the error message having > to be "long enough". It might be cache settings, but my Chromium definitely does not show a "default message" if I get a 204 with zero bytes, it keeps displaying the old content (if the url is the same). Developer Tools of course show this, but not the actual contents of the browser tab.