Nginx v1.8.0 / redirects

How do I best:

1.> redirect > www.
a.) if www is already present, skip to step 2

2.> redirect http://www. request > https://…

??? Thanks.

  • Fabian S.

thanks. worked like a charm!

I would suggest you avoid multiple redirects in the case a client
connects
with http://domain, because your current setup will make the client
following this flow:
http://domain > http://www.domain > https://www.domain

This will hurt your TTFB. I suggest your first redirect should directly
point to the HTTPS scheme.

B. R.

On Tue, Sep 01, 2015 at 04:41:20PM -0400, remo[email protected]
wrote:

Hi there,

1.> redirect > www.
a.) if www is already present, skip to step 2

2.> redirect http://www. request > https://…

http://nginx.org/en/docs/http/server_names.html

Use two server{} blocks.

One matches only www.* and redirects to https://$host$request_uri

The other redirects to http://www.$host$request_uri

f

Francis D. [email protected]

I hear what you’re saying. i will do that instead and test it out. thank
you.

– Fabian S.

On 2015-09-02 03:02, B.R. wrote:

Use two server{} blocks.

One matches only www.* and redirects to https://$host$request_uri

The other redirects to http://www. [6]$host$request_uri

f


nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx [7]


nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx [7]

Links:

[1] http://domain
[2] http://www.domain
[3] https://www.domain
[4] http://www
[5] http://nginx.org/en/docs/http/server_names.html
[6] http://www.
[7] http://mailman.nginx.org/mailman/listinfo/nginx

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs