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: > I would suggest you avoid multiple redirects in the case a client connects > with http://domain [1], because your current setup will make the client > following this flow: > http://domain [1] > http://www.domain [2] > https://www.domain [3] > > This will hurt your TTFB. I suggest your first redirect should directly point > to the HTTPS scheme. > > --- > B. R. > > On Wed, Sep 2, 2015 at 3:33 AM, <fsanti...@deviltracks.net> wrote: > thanks. worked like a charm! > > On 2015-09-01 17:16, Francis Daly wrote: > On Tue, Sep 01, 2015 at 04:41:20PM -0400, fsanti...@deviltracks.net wrote: > > Hi there, > > 1.> redirect <domain> > www.<domain> > a.) if www is already present, skip to step 2 > > 2.> redirect http://www [4].<domain> request > https://...... > http://nginx.org/en/docs/http/server_names.html [5] > > 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 nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx [7] _______________________________________________ nginx mailing list nginx@nginx.org 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
_______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
