A fatal 301 redirect...

Pierre Couderc pierre at couderc.eu
Tue Sep 18 05:10:17 UTC 2018

On 09/18/2018 02:55 AM, Maxim Dounin wrote:
> 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
>> 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).
Mmm... I double check
>> - There are no "secret caches" in nginx.  The only caches are ones
>>    explicitly configured using coresponding configuration
>> directives - us
Thank you, I needed thsi answer.
>> ually 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.
Oh, I have well reloaded or restarted  nginx 10 or 100 times !!
>> - If in doubt, looking into full configuration as show with "nginx
>>    -T" might help.
Oh yes, after painfull experience (all sites stopped!!), I never change 
a line in config file without testing it thyis way!!
>>   If still in doubt, the most advanced (yet
>> low-level) instrument is debug log
>> (http://nginx.org/en/docs/debugging_log.html).
Thank you, this is the only way...

Thank you to help me to think.

More information about the nginx mailing list