[IE] Re: Rewrite with number after hyphen

[Jason Whittington]

FWIW when I debug this sort of thing I like to emit a response header identifying which rule is routing the request, like this:

location /a/ {
   add_header X-nginx-debug /a/
   proxy_pass http://whatever/;
}

That way you can use F12 tools or some other inspection on the result and see exactly what is triggering.  This has saved my bacon more than once ☺.

Jason


> > location /foo {
> > rewrite /foo/(.*) /web/foo.do?a=$1 last;
> > }

From: nginx [mailto:nginx-bounces at nginx.org] On Behalf Of Ivan Bianchi
Sent: Wednesday, September 5, 2018 9:25 AM
To: nginx at nginx.org
Subject: [IE] Re: Rewrite with number after hyphen

Hi Francis,

many thanks for your response and guidelines. Indeed you were right that there was another location capturing the request.

Best regards,

On Mon, Sep 3, 2018 at 2:36 PM Francis Daly <francis at daoine.org<mailto:francis at daoine.org>> wrote:
On Mon, Sep 03, 2018 at 08:13:11AM +0200, Ivan Bianchi wrote:

Hi there,

> > location /foo {
> > rewrite /foo/(.*) /web/foo.do?a=$1 last;
> > }

This seems to work as expected for me, using nginx/1.14.0.<http://1.14.0.>

> KO:
>
> > https://www.test.com/foo/asdf-12

Why do you think it does not work? What is the input/output/expected
output?

For example, if you add the new location

   location = /web/foo.do {
      return 200 "$uri$is_args$args\n";
   }

and repeat the tests, do you see any difference in output?

> Why if I put a number after a hyphen the regex stops working?

My guesses are:

* you have another location{} that you have configured to match those
requests, so your shown location{} is not involved

or

* your /web/foo.do location-handler handles those requests differently.

Good luck with it,

        f
--
Francis Daly        francis at daoine.org<mailto:francis at daoine.org>
_______________________________________________
nginx mailing list
nginx at nginx.org<mailto:nginx at nginx.org>
http://mailman.nginx.org/mailman/listinfo/nginx


--
Ivan Bianchi
Wikiloc
This message contains proprietary information from Equifax which may be confidential. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e-mail postmaster at equifax.com. Equifax® is a registered trademark of Equifax Inc. All rights reserved.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20180905/af2fdae5/attachment-0001.html>