How can I overload the default html output for 301 header code?
I try this:
error_page 301 /nginx-default/301.html;
but 301 must be between 400 and 599
How can I overload the default html output for 301 header code?
I try this:
error_page 301 /nginx-default/301.html;
but 301 must be between 400 and 599
Hello!
On Wed, Jul 02, 2008 at 07:43:51AM -0300, Marcos N. wrote:
How can I overload the default html output for 301 header code?
I try this:
error_page 301 /nginx-default/301.html;but 301 must be between 400 and 599
http://mdounin.ru/files/patch-nginx-errorpage
Not sure it’s still applies cleanly to latest nginx. This was
written to serve wap/wml sites through nginx (needed since 3xx
replies must be wml for some phones) and basically does
two things:
Allows error_page definitions for 3xx codes.
Implements correct work of proxy_intercept_errors with 301/302
codes.
Maxim D.
Any chance this could become part of the trunk? I can see the features
described being useful in future versions of nginx.
Maxim D. wrote:
–
Phillip B Oldham
The Activity People
[email protected] mailto:[email protected]
Policies
This e-mail and its attachments are intended for the above named
recipient(s) only and may be confidential. If they have come to you in
error, please reply to this e-mail and highlight the error. No action
should be taken regarding content, nor must you copy or show them to
anyone.
This e-mail has been created in the knowledge that Internet e-mail is
not a 100% secure communications medium, and we have taken steps to
ensure that this e-mail and attachments are free from any virus. We must
advise that in keeping with good computing practice the recipient should
ensure they are completely virus free, and that you understand and
observe the lack of security when e-mailing us.
Hello!
On Wed, Jul 02, 2008 at 02:54:06PM +0100, Phillip B Oldham wrote:
Any chance this could become part of the trunk? I can see the features
described being useful in future versions of nginx.
Igor is aware of this patch since it’s creation (and the patch
itself is used in Rambler), but he was planning to rewrite some of
the affected parts (proxy module) and wasn’t in position to import
it till this happens.
Probably import may happen sometime after cache release, but I’m not
aware of current Igor’s plans about it.
Maxim D.
but 301 must be between 400 and 599
not a 100% secure communications medium, and we have taken steps to
ensure that this e-mail and attachments are free from any virus. We must
advise that in keeping with good computing practice the recipient should
ensure they are completely virus free, and that you understand and
observe the lack of security when e-mailing us.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs