too many redirects

[B.R.]

Maybe start over your configuration, one step at a time, checking
everything you do has the desirect effect?
Step by step, gently, no pressure. That is the way you learn! Do not give
up, if you need specific help people are here to help you :o)

As you just realized, copy-pasting 'magic' configuration snippets from
other people does not always works out of the box. That demosntrates the
fact that copy-pasting != learning :o)

By the way, the 'if' directive is tricky and to be avoided as much as
possible. It is used for very speicifc cases, when you cannot do anyway
else. I have not read thoroughly the link you provided, however by having a
quick look it seemed to me I saw a lot of (too much?) 'if'...

Start with a simple, but working configuration, and solve one
requirement/issue at a time!
Good luck,
---
*B. R.*

On Thu, Nov 20, 2014 at 10:07 PM, JACK LINKERS <jacklinkers at gmail.com>
wrote:

> I completely lost...
> I tried everything (of my understanding) with no success.
> I didn't know you could include a condition with if and came across sites
> like :
>
> http://publications.jbfavre.org/web/nginx-vhosts-automatiques-avec-SSL-et-authentification.fr
> This is way beyond my skills... I didn't managhe to enclose the 301 in if
> statements
> I think i'm gonna givin up
>
> 2014-11-20 10:27 GMT+01:00 JACK LINKERS <jacklinkers at gmail.com>:
>
>> Hi guys,
>>
>> Thanks for your fast reply and input.
>> I didn't think of wordpress at all.
>>
>> I'll try some tuning and keep you posted.
>>
>> Thanks again
>> Le 20 nov. 2014 09:52, "B.R." <reallfqq-nginx at yahoo.fr> a écrit :
>>
>>> On Thursday, November 20, 2014, JACK LINKERS <jacklinkers at gmail.com>
>>>> wrote:
>>>>
>>>>> rewrite     ^   https://$server_name$request_uri? permanent;
>>>>>
>>>>
>>> ​This looks highly suscpicious to me: unconditional rewrite of any
>>> request?
>>>
>>> Try to either:
>>> - match the regex against HTTP requests
>>> - enclose a 'return 301 [...]' in an 'if' directive checking for the
>>> HTTP scheme
>>> I am not 100% certain what would be the best alternative to go for.
>>>
>>> If the problem comes from there, I do not really get how the backend
>>> gets to serve any (error) page... So maybe Wordpress trouble as stated
>>> before.
>>> ---
>>> *B. R.*
>>> ​
>>>
>>>
>>> _______________________________________________
>>> nginx mailing list
>>> nginx at nginx.org
>>> http://mailman.nginx.org/mailman/listinfo/nginx
>>>
>>
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20141120/2c26ee35/attachment.html>