Change in error_page behavior

Server NGINX
1

I used to use this:

  error_page 497 https://domain.com:7878$request_uri;

to redirect requests from the http://domain.com:7878 non-ssl address to
the ssl version on the same port. see
Http->https redirection on the same port - NGINX - Ruby-Forum

This stopped working recently, probably with the latest change to
error_page in 0.8.53.

After some trial and error, it seems to be working fine with this:

  error_page 497 =301 https://domain.com:7878$request_uri;

Is that going to give me the same effect as before?

Posted at Nginx Forum:

2

Hello!

On Mon, Nov 01, 2010 at 02:20:56PM -0400, brianmercer wrote:

I used to use this:

  error_page 497 https://domain.com:7878$request_uri;

to redirect requests from the http://domain.com:7878 non-ssl address to
the ssl version on the same port. see
Http->https redirection on the same port - NGINX - Ruby-Forum

This stopped working recently, probably with the latest change to
error_page in 0.8.53.

Yes, thank you for your report. It’s indeed broken in 0.8.53.

I’m currently working on a patch for another problem introduced by
the same change, it should fix your problem as well.

After some trial and error, it seems to be working fine with this:

  error_page 497 =301 https://domain.com:7878$request_uri;

Is that going to give me the same effect as before?

If you want to achieve exactly the same effect as before you
should use =302. Though =301 is probably better here.

Maxim D.

3

Hello!

On Tue, Nov 02, 2010 at 01:05:42AM +0300, Maxim D. wrote:

Http->https redirection on the same port - NGINX - Ruby-Forum

This stopped working recently, probably with the latest change to
error_page in 0.8.53.

Yes, thank you for your report. It’s indeed broken in 0.8.53.

I’m currently working on a patch for another problem introduced by
the same change, it should fix your problem as well.

Patch:

http://nginx.org/pipermail/nginx-devel/2010-November/000537.html

Maxim D.