One. Problem Description:
Chrome sends a construction string to the server and returns the error page as follows
1 <HTML>2 <Head>3 <title>404 Not Found</title>4 </Head>5 <Bodybgcolor= "White">6 <Center>7 <H1>404 Not Found</H1>8 </Center>9 <HR>Ten <Center>nginx/1.6.2</Center> One </Body> A </HTML> - <!--a padding to disable MSIE and Chrome friendly error page - - <!--a padding to disable MSIE and Chrome friendly error page - the <!--a padding to disable MSIE and Chrome friendly error page - - <!--a padding to disable MSIE and Chrome friendly error page - - <!--a padding to disable MSIE and Chrome friendly error page - - <!--a padding to disable MSIE and Chrome friendly error page -
Here's the question, what's the last six lines of comment?
Two. Why is this problem occurring?
Iebug #11289 always pad the error page with enough characters such that it's greater than, bytes after gzip compression.
That is, when a browser receives a packet that is smaller than the threshold set by IE, it does not render the contents of the package, but instead displays it in IE's built-in error page, such as a networking error. This way the front end cannot correctly determine the type of error.
Three. Solve.
In the Internet option, uncheck the show friendly HTTP error message option.
*****
Reference.
Code |
Description |
file Size (threshold value) |
400 |
Bad Request |
> bytes |
403 |
Forbidden |
> bytes |
404 |
Not Found |
> bytes |
405 |
Method not allowed |
> bytes |
50W |
Not acceptable |
> bytes |
408 |
Request time-out |
> bytes |
409 |
Conflict |
> bytes |
410 |
Gone |
> bytes |
500 |
Internal Server Error |
> bytes |
30w |
Not implemented |
> bytes |
505 |
HTTP Version not supported |
> bytes |
These configurations are in the registry.
Custom HTTP error page is too small to display the default friendly error page problem