Hello!

On Tue, Sep 18, 2018 at 12:10:22AM +0200, Pierre Couderc 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 ?

In no particular order:

- There are no log lines in the access log coresponding to the
requests you've made with wget. This means that either you are
connecting to the wrong server (check the IP address) or logging
is not properly configured (check your logging configuration).

- There are no "secret caches" in nginx. The only caches are ones
explicitly configured using coresponding configuration
directives - usually proxy_cache for HTTP proxying.

- A common mistake is to change configuration without actually
reloading it. Make sure to reload the configuration after
changes, and make sure to look into error log to find out if it
was actually reloaded or the configuration reload failed.

- If in doubt, looking into full configuration as show with "nginx
-T" might help. If still in doubt, the most advanced (yet
low-level) instrument is debug log
(http://nginx.org/en/docs/debugging_log.html).

--
Maxim Dounin
http://mdounin.ru/
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx