Lines Matching refs:error_page
134 *) Bugfix: a socket leak might occur when using the "error_page"
139 returning errors if the request was redirected by the "error_page"
405 intercepted by error_page.
517 *) Feature: the "return" and "error_page" directives can now be used to
1761 "error_page" directive.
2553 *) Feature: the "return" and "error_page" directives can now be used to
2653 URI after redirection with the "error_page" directive.
3160 *) Bugfix: an "error_page" directive did not work with nonstandard error
3235 *) Feature: now the "error_page" directive allows to change a status
3294 *) Bugfix: errors intercepted by error_page were cached only for next
3335 *) Bugfix: errors intercepted by error_page could not be cached.
3391 *) Bugfix: an error_page redirection to "location /zero {return 204;}"
3633 *) Feature: now the "error_page" directive may redirect the 301 and 302
3963 *) Bugfix: an "error_page" directive did not redirect a 413 error; the
4327 *) Bugfix: the "error_page" directive made an external redirect without
4384 request was redirected to a proxied or FastCGI server via error_page
4671 error_page directive.
4864 "error_page" directive.
4867 redirection via an "error_page" directive.
4899 *) Bugfix: of recursive error_page for 500 status code.
5116 *) Bugfix: the "error_page" directive did not take into account
5145 named location via an "error_page" directive.
5160 *) Bugfix: if response code 495-497 was redirected via an "error_page"
5402 *) Bugfix: if the "?" character was in a "error_page" directive, then it
5430 "error_page" directive, then nginx tried to read the request body
6299 *) Bugfix: after redirecting error by an "error_page" directive any
6319 *) Bugfix: the "return" directive always overrode the "error_page"
6320 response code redirected by the "error_page" directive.
6332 "error_page" directive.
6409 "error_page" directive.
6413 *) Bugfix: the "error_page" directive did not changes the "Content-Type"
6420 *) Feature: the "error_page" directive supports the variables.
6427 *) Bugfix: the "error_page" directive did not redirect the 413 error.
7348 *) Feature: the "error_page" directive supports redirects and allows