atom feed21 messages in ru.sysoev.nginxRe: Custom 503 Error Page
FromSent OnAttachments
Douglas A. SeifertFeb 2, 2008 3:18 pm 
Maxim DouninFeb 2, 2008 4:36 pm 
Douglas A. SeifertFeb 2, 2008 5:08 pm 
Maxim DouninFeb 2, 2008 5:20 pm 
Eden LiFeb 2, 2008 5:22 pm 
Douglas A. SeifertFeb 2, 2008 6:14 pm 
Douglas A. SeifertFeb 2, 2008 6:15 pm 
Maxim DouninFeb 2, 2008 6:33 pm 
Eden LiFeb 2, 2008 6:47 pm 
Maxim DouninFeb 2, 2008 7:15 pm 
Douglas A. SeifertFeb 2, 2008 8:02 pm 
Corey DonohoeFeb 2, 2008 10:39 pm 
Igor SysoevFeb 2, 2008 10:40 pm 
Douglas A. SeifertFeb 3, 2008 7:51 am 
Douglas A. SeifertFeb 3, 2008 7:58 am 
Corey DonohoeFeb 3, 2008 9:59 am 
Doug SeifertFeb 3, 2008 1:36 pm 
Killian MurphyJun 19, 2009 9:47 pm 
Spirit SpiritNov 26, 2009 2:31 pm 
Igor SysoevNov 26, 2009 10:02 pm 
spiritDec 2, 2009 1:46 pm 
Subject:Re: Custom 503 Error Page
From:Eden Li (eden@public.gmane.org)
Date:Feb 2, 2008 6:47:16 pm
List:ru.sysoev.nginx

Hmm... that doesn't seem to work either. Is it possible that `return xxx;` always generates the internal response?

The only thing that would achieve the desired result in this case is proxying to some blackhole which would cause the 503 to be caught and rewritten according to the error_page directive.

On Feb 3, 2008, at 10:34 AM, Maxim Dounin wrote:

Just another quick note: due to some implementation wierdness of ngx_http_rewrite_module, it may be required to define error_page _before_ if/return block. Try something like this:

error_page 503 /system/maintenance.html;

if (-f ...) { return 503; }