If by dns record, you mean uwsgi_pass, then yea, I'm sure. Otherwise
localhost wouldn't work either, but it does.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,278386,278408#msg-278408
___
nginx mailing list
nginx@nginx.org
http://mailman.n
Hmmm!
>>> location ~* wp-login\.php$ {
>>
>>> 185.124.153.168 - - [05/Feb/2018:21:36:12 +0100] "GET /wp-login.php
>>> HTTP/1.1" 200 1300 "-" "Mozilla/5.0 (Windows NT 6.0; rv:34.0)
>>> Gecko/20100101 Firefox/34.0"
>>
>>> Me too :-(
>>
>> Have you any reason to believe that this location is use
I find that add_header always works well to verify that the location is being
chosen the way you think.
Try something like
add_header X-NGINX-Route always;
to some of your location blocks and specify different distinct values for
.
Then in your browser you can use F12 tools to verify that
Hi Francis,
>> location ~* wp-login\.php$ {
>
>> 185.124.153.168 - - [05/Feb/2018:21:36:12 +0100] "GET /wp-login.php
>> HTTP/1.1" 200 1300 "-" "Mozilla/5.0 (Windows NT 6.0; rv:34.0) Gecko/20100101
>> Firefox/34.0"
>
>> Me too :-(
>
> Have you any reason to believe that this location is used t
On Wed, Feb 07, 2018 at 09:57:04PM +0530, Kaushal Shriyan wrote:
> On Wed, Feb 7, 2018 at 5:32 AM, Francis Daly wrote:
> > On Mon, Feb 05, 2018 at 11:56:04PM +0530, Kaushal Shriyan wrote:
Hi there,
> In the curl request I am adding http header -H 'x-forwarded-for:
> 12.12.12.13.11'
>
> curl -X
On Wed, Feb 7, 2018 at 5:32 AM, Francis Daly wrote:
> On Mon, Feb 05, 2018 at 11:56:04PM +0530, Kaushal Shriyan wrote:
>
> Hi there,
>
> > When i run this curl call -> curl -X GET http://13.127.165.226/ -H
> > 'cache-control: no-cache' -H 'postman-token:
> > 2494a4a7-6791-2426-cedf-d0bcaa1cd90a'
On Wednesday 07 February 2018 00:08:03 Credo wrote:
> Sorry, I posted the wrong configuration. I did add the server_name I was
> using. I just changed it to localhost to see what happens. But when the
> server name was the one I was using, I only got time outs!
Are you sure that DNS record points
