Thanks for the reply and I'm sorry! It was my fault that I didn't see
that text in the documentation.
"These directives are inherited from the previous level if and only if
there are no error_page directives defined on the current level."
On Fri, Aug 7, 2020 at 4:05 AM Francis Daly wrote:
>
> On
On Thu, Aug 06, 2020 at 09:43:46PM -0300, Fabiano Furtado Pessoa Coelho wrote:
Hi there,
> http {
> error_page 502 503 /my503.html;
> ...
> server {
> ...
> error_page 403 =503 /my503.html;
> #error_page 502 503 /my503.html;
> I can solve this issue uncommenting the "#error_pa
Hi...
I have the following setup in my NGINX 1.18.0 server:
http {
...
error_page 400 /my400.html;
error_page 401 /my401.html;
error_page 403 /my403.html;
error_page 404 /my404.html;
error_page 405 /my405.html;
error_page 413 /my413.html;
error_page 500
Whoops!
Minimal test configuration FTW... There was a '/' prefix location block
hidden at the bottow of my server one, with an ugly 'try_files $uri.php
=404;' directive...
As notes, though :
I removed the '=' parameter from the error_page directive to simplify, as
there is no special processing d
On Mon, Apr 04, 2016 at 08:54:12PM +0100, Francis Daly wrote:
> On Mon, Apr 04, 2016 at 09:36:36PM +0200, B.R. wrote:
Hi there,
> > -> Error page HTTP 404 (???)
>
> I only get 404 if error_page.html does not exist. If it does exist,
> I get it with http 200.
>
> Aside from that: I suspect that
On Mon, Apr 04, 2016 at 09:36:36PM +0200, B.R. wrote:
Hi there,
> I am struggling to understand the error_page directive behavior:
I do not get the full same results that you report, when I use 1.9.2.
> Expected behavior:
> ->Request to http://example.com/proxy
> -> Sub-request to http://ex
Hello,
I am struggling to understand the error_page directive behavior:
​server {
listen 80;
listen [::]:80;
server_name example.org;
location /proxied {
return 418 "Host: $host, Connection: $http_connection";
}
}
server {
listen 80;
listen
