# "error\_page"& "return" bug? **URL:** \ **Category:** NGINX\ **Created:** [February 19, 2012, 11:23am UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006 "2012-02-19T11:23:15Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![dubstep](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/cdc98d/32.png) [@dubstep](https://www.ruby-forum.com/u/dubstep)\ **Post date:** [February 19, 2012, 11:23am UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/1 "2012-02-19T11:23:15Z")
Hello, It appears that the error\_page directive is ignored when a status code is returned in the server context. (running v1.0.12 Stable). Server { # listen etc … error\_page 503 /error\_docs/custom503.html; return 503 location /error\_docs { internal; alias /server/path/to/folder; } … } Will always return the Nginx default 503 page. Same applies to all status codes. When the status code is returned within a location block, the custom page is shown as expected … Server { # listen etc … error\_page 503 /error\_docs/custom503.html; location / { return 503; } location /error\_docs { internal; alias /server/path/to/folder; } … } ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 1:03pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/2 "2012-02-19T13:03:34Z")
Hello! On Sun, Feb 19, 2012 at 01:22:34PM +0300, Nginx U. wrote: > return 503 > location /error\_docs { > internal; > alias /server/path/to/folder; > } > > … > } > > Will always return the Nginx default 503 page. Same applies to all status codes. It’s not ignored, but returning error unconditionally in the server context also prevents error\_page processing from working, as the “return 503” is again executed after error\_page internal redirect. That is, something like this happens: 1. Request comes for “/something”. 2. Server rewrites generate 503. 3. Due to error\_page set the request is internally redirected to /error\_docs/custom503.html. 4. Server rewrites again generate 503. 5. As we’ve already did error\_page redirection, nginx ignores error\_page set and returns internal error page. > } > location /error\_docs { > internal; > alias /server/path/to/folder; > } > > … > } This doesn’t “return 503” for error\_page processing, and hence it works ok. Another possible aproach is to use named location in error\_page. It won’t re-execute server rewrites (that is, rewrite module directives, including the “return” directive, specified at server level) and will work as well. Maxim D. ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 1:24pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/3 "2012-02-19T13:24:37Z")
On 19 February 2012 15:03, Maxim D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > 1. Server rewrites again generate 503. > 2. As we’ve already did error\_page redirection, nginx ignores > error\_page set and returns internal error page. This then is the “bug”. It SHOULD now return “/error\_docs/custom503.html” with a 503 status code. I.E., work as it does when the error is issued within a location context since once a user has set error\_page, they would most likely expect a matching status return to deliver what was set. I assume there must be some technical road block but you guys are supposed to be geniuses 🙂 Can’t wait for the solution!! ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 1:46pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/4 "2012-02-19T13:46:21Z")
On 19 February 2012 15:03, Maxim D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Another possible aproach is to use named location in error\_page. > It won’t re-execute server rewrites (that is, rewrite module > directives, including the “return” directive, specified at server > level) and will work as well. Unfortunately, this doesn’t appear to work as expected either Server { # listen etc … ``` error_page 503 = @sitedown; return 503 location @sitedown { root /server/path/to/folder; # Don't you wish try_files could accept a single ``` parameter? try\_files $uri /custom503.html; } ``` ... ``` } ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 1:56pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/5 "2012-02-19T13:56:17Z")
Hello! On Sun, Feb 19, 2012 at 03:23:58PM +0300, Nginx U. wrote: > > /error\_docs/custom503.html. > > 4. Server rewrites again generate 503. > > 5. As we’ve already did error\_page redirection, nginx ignores > > error\_page set and returns internal error page. > > This then is the “bug”. > It SHOULD now return “/error\_docs/custom503.html” with a 503 status code. > I.E., work as it does when the error is issued within a location > context since once a user has set error\_page, they would most likely > expect a matching status return to deliver what was set. This is not a bug. You instructed nginx to generate 503 on each request which hits server rewrite phase, and it does what you said. Maxim D. ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 2:00pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/6 "2012-02-19T14:00:39Z")
On 19 February 2012 15:45, Nginx U. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > … > } > PS. In any case, it would not be an ideal solution even if it did work as it would return a “200” status code with the custom file. So getting things to work as with the location option is probably best. In the interim, I have managed to get it to work by first redirecting to a location and issuing the 503 status code there Server { error\_page 503 /error\_docs/custom503.html; rewrite ^ /sitedown/ redirect; location /sitedown { return 503 } location /error\_docs { internal; alias /server/path/to/error\_docs/folder; } } ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 2:04pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/7 "2012-02-19T14:04:58Z")
Hello! On Sun, Feb 19, 2012 at 03:45:15PM +0300, Nginx U. wrote: > ``` > ... > > error_page 503 = @sitedown; > return 503 > location @sitedown { > root /server/path/to/folder; > # Don't you wish try_files could accept a single parameter? > try_files $uri /custom503.html; > > ``` Unless you have $uri file, this will do an internal redirect to /custom503.html, triggering the same 503 again. You have to process request in the location in question to make things work. Maxim D. ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 2:07pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/8 "2012-02-19T14:07:27Z")
On 19 February 2012 16:04, Maxim D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > Unfortunately, this doesn’t appear to work as expected either > > try\_files $uri /custom503.html; > > Unless you have $uri file, this will do an internal redirect to > /custom503.html, triggering the same 503 again. You have to > process request in the location in question to make things work. Thanks. I got a working config where I first redirect to a location and issue the 503 status there. Now, don’t you really, really wish try\_files could accept a single parameter?? 🙂 Thanks for your help. ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 1:26pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/9 "2012-02-19T13:26:29Z")
On 19 February 2012 15:23, Nginx U. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Can’t wait for the solution!! I’ll try the named location suggestion first of course ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 2:56pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/10 "2012-02-19T14:56:27Z")
On Sun, Feb 19, 2012 at 8:06 PM, Nginx U. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Thanks. > > I got a working config where I first redirect to a location and issue > the 503 status there. What’s the problem with placing return 503 in location / { } block? – O\< ascii ribbon campaign - stop html mail - [www.asciiribbon.org](http://www.asciiribbon.org) ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 3:47pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/11 "2012-02-19T15:47:14Z")
On Sun, Feb 19, 2012 at 9:01 PM, Nginx U. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > What’s the problem with placing return 503 in location / { } block? > > None whatsoever. Did anyone say there was one? Just wondering. Also I couldn’t make the method with rewriting work. I got 302’d ad infinitum. – O\< ascii ribbon campaign - stop html mail - [www.asciiribbon.org](http://www.asciiribbon.org) ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 3:02pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/12 "2012-02-19T15:02:39Z")
On 19 February 2012 16:55, Edho A. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > On Sun, Feb 19, 2012 at 8:06 PM, Nginx U. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > > Thanks. > > > > I got a working config where I first redirect to a location and issue > > the 503 status there. > > What’s the problem with placing return 503 in location / { } block? None whatsoever. Did anyone say there was one? ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 4:10pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/13 "2012-02-19T16:10:13Z")
On 19 February 2012 18:06, Nginx U. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > This is what actually works: Small amendment: Server { error\_page 503 /error\_docs/custom503.html; if ( $request\_uri !~ .(gif|png|css|js)$ ) { set $m “T”; } if ( $request\_uri !~ ^/maintenance/$ ) { set $maint “${maint}T”; } if ( $maint = TT ) { rewrite ^ /maintenance/ redirect; } location /maintenance { internal; return 503; } location /error\_docs { internal; alias /server/path/to/error\_docs/folder; } } ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 4:13pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/14 "2012-02-19T16:13:20Z")
Sorry … Server { error\_page 503 /error\_docs/custom503.html; if ( $request\_uri !~ .(jpg|gif|png|css|js)$ ) { set $tt “T”; } if ( $request\_uri !~ ^/maintenance/$ ) { set $tt “${maint}T”; } if ( $tt = TT ) { rewrite ^ /maintenance/ redirect; } location /maintenance { internal; return 503; } location /error\_docs { internal; alias /server/path/to/error\_docs/folder; } } ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 4:07pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/15 "2012-02-19T16:07:44Z")
On 19 February 2012 17:46, Edho A. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > On Sun, Feb 19, 2012 at 9:01 PM, Nginx U. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > > > What’s the problem with placing return 503 in location / { } block? > > > > None whatsoever. Did anyone say there was one? > > Just wondering. Also I couldn’t make the method with rewriting work. I > got 302’d ad infinitum. That’ll be because none of the code I posted is actually real. They were just to help get an answer. This is what actually works: Server { error\_page 503 /error\_docs/custom503.html; if ( $request\_uri !~ .(jpg|gif|png|css|js)$ ) { set $tt “T”; } if ( $request\_uri !~ ^/maintenance/$ ) { set $tt “${tt}T”; } if ( $tt = TT ) { rewrite ^ /maintenance/ redirect; } location /maintenance { internal; return 503; } location /error\_docs { internal; alias /server/path/to/503\_status/folder; } } ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 4:21pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/16 "2012-02-19T16:21:28Z")
Arrggghhh! Server { error\_page 503 /error\_docs/custom503.html; if ( $request\_uri !~ .(jpg|gif|png|css|js)$ ) { set $tt “T”; } if ( $request\_uri !~ ^/maintenance/$ ) { set $tt “${tt}T”; } if ( $tt = TT ) { rewrite ^ /maintenance/ redirect; } location /maintenance { internal; return 503; } location /error\_docs { internal; alias /server/path/to/error\_docs/folder; } } Finally I promise 🙂 ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 4:55pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/17 "2012-02-19T16:55:35Z")
Nevermind, I just got this awesome idea: if ($uri !~ ^/error\_page/) { return 503; } (seems to be working on my simple test) On Sun, Feb 19, 2012 at 10:23 PM, Edho A. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > } > location /error\_docs/ { > internal; > alias /server/path/to/error\_docs/folder; > } > } > ############# – O\< ascii ribbon campaign - stop html mail - [www.asciiribbon.org](http://www.asciiribbon.org) ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 5:37pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/18 "2012-02-19T17:37:50Z")
On 19 February 2012 18:54, Edho A. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > ############# > > } > > ############# Your method will work if you only a few location blocks active to which you can easily add the return directive. The one I suggested works in my case where I have several location blocks. I have just put the relevant bits into a file and can include it when I need to take the domain down. It also allows for the inclusion of images, css. js and similar resources. With these things, there is no single answer. ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 5:45pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/19 "2012-02-19T17:45:17Z")
On Sun, Feb 19, 2012 at 11:37 PM, Nginx U. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > > alias /server/path/to/error\_docs/folder; > > > } > > > } > > > ############# > > Your method will work if you only a few location blocks active to > which you can easily add the return directive. You can nest all your location blocks in single location / { } block (and you can put location / { } in location / { }). Just add “location / {” before start of other locations (except error page) and “}” after them. Also have you tried this one? Instead of plain “return 503;” in server block: server { if ($uri !~ ^/error\_page/) { return 503; } … } Because even if “return 503” is capable of returning the page you want, the css/js/image still won’t work. – O\< ascii ribbon campaign - stop html mail - [www.asciiribbon.org](http://www.asciiribbon.org) ---
**Author:** ![Nginx\_U](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@Nginx\_U](https://www.ruby-forum.com/u/Nginx_U)\ **Post date:** [February 19, 2012, 6:20pm UTC](https://www.ruby-forum.com/t/error-page-return-bug/217006/20 "2012-02-19T18:20:07Z")
On 19 February 2012 19:44, Edho A. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Also have you tried this one? Instead of plain “return 503;” in server block: > No, I haven’t and don’t plan to at this time because I have a setup > that works fine as posted earlier with images, css etc all loading as > required. As said, there isn’t one single answer as the Nginx config allows a lot of flexibility and if you prefer a different setup, that’s just fine. All the best! [Next page](https://www.ruby-forum.com/t/error-page-return-bug/217006.md?page=2)