On Wed, Feb 07, 2018 at 07:28:37PM +0100, Ph. Gras wrote:
Hi there,
> >> 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 to handle this
> > request?
>
> Yes, and this especially since before, it worked as expected :-(
I see in other mail that that has become fixed -- probably this location
was not being used for this request, owing to an earlier "location ~
php", or something else that was changed since it had been working before.
> > $ nginx -T | grep 'server\|location'
> >
> > will possibly give a useful hint in that direction.
>
> # nginx -T | grep "www.example.com/wp-login.php"
> nginx: invalid option: "T"
I actually meant literally "grep 'server\|location'", to show the
server{} blocks (and server_name directives) and the location directives
in your config, which might be enough to show which location{} is used
for one request.
But your nginx version is from before "-T" was added, so you would have
to look in the config file (and any include:d files) directly, and there
isn't a simple one-liner to do that.
And now that it works for you, it is not important any more :-)
f
--
Francis Daly fran...@daoine.org
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
