Welcome! Log In Create A New Profile

Advanced

Re: A fatal 301 redirect...

September 17, 2018 06:22PM
I think this problem is better solved allowing 80 to be open and a separate
server block. Since i terminate from haproxy, from memory something like
this, in the same vhost file. Obviously you can listen here on H/2 if you
want to as well.

server {
listen 80 default_server;
server_name test.ppp.fr;
return 301 https://$server_name$request_uri;
}

Best,
jeff

On Mon, Sep 17, 2018 at 6:10 PM Pierre Couderc <pierre@couderc.eu> wrote:

> I did use wrongly a 301 redirect....
>
> I have corrected now, but the redirect remains.
>
> I use wget :
>
> nous@pcouderc:~$ wget https://www.ppp.fr
> --2018-09-17 23:52:44-- https://www.ppp.fr/
> Resolving www.ppp.fr (www.ppp.fr)... 2a01:e34:eeaf:c5f0::fee6:854e,
> 78.234.252.95
> Connecting to www.ppp.fr
> (www.ppp.fr)|2a01:e34:eeaf:c5f0::fee6:854e|:443... connected.
> HTTP request sent, awaiting response... 301 Moved Permanently
> Location: https://test.ppp.fr/ [following]
> --2018-09-17 23:52:44-- https://test.ppp.fr/
> Resolving test.ppp.fr (test.ppp.fr)... 2a01:e34:eeaf:c5f0::fee6:854e,
> 78.234.252.95
> Connecting to test.ppp.fr
> (test.ppp.fr)|2a01:e34:eeaf:c5f0::fee6:854e|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [text/html]
> Saving to: ‘index.html.3’....
>
> In access.log :
>
> 2a01:e34:eeaf:c5f0::feb1:b1c9 - - [18/Sep/2018:00:04:34 +0200] "GET /
> HTTP/2.0" 200 21511 "-" "Mozilla/5.0 (X11; Linux x86_64)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36"
> 2a01:e34:eeaf:c5f0::feb1:b1c9 - - [18/Sep/2018:00:04:34 +0200] "GET
> /fuveau.png HTTP/2.0" 404 271 "https://test.ppp.fr/" "Mozilla/5.0 (X11;
> Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81
> Safari/537.36"
>
>
> I am pretty sure that I have removed the fatal redirect, and I have
> checked that the only 301 remaining are on port 80 :
> location / {
> return 301 https://$server_name$request_uri;
> }
>
> So I suppose there is a cache somewhere where nginx keeps its secret and
> fatal 301 ? How can I remove it ?
>
> Thanks
>
> PC
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

A fatal 301 redirect...

Pierre Couderc September 17, 2018 06:12PM

Re: A fatal 301 redirect...

jeffdyke September 17, 2018 06:22PM

Re: A fatal 301 redirect...

Maxim Dounin September 17, 2018 08:56PM

Re: A fatal 301 redirect...

Pierre Couderc September 18, 2018 01:12AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 62
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready