Hello!
On Wed, Apr 07, 2021 at 05:16:20PM -0700, Demitrious Kelly wrote:
> Thanks very much. It was not an easy thing to google to get
> from symptom to bug report :) From the text in the ticket it
> sounds like the named capture functions as intended and if this
> bug gets fixed the numeric
gin forwarded message:
>
> From: Maxim Dounin
> Subject: Re: Capturing Encoded Location Variable Data
> Date: April 7, 2021 at 4:13:58 PM PDT
> To: nginx@nginx.org
> Reply-To: nginx@nginx.org
>
> Hello!
>
> On Wed, Apr 07, 2021 at 03:07:34PM -0700, Demitrious Kelly
Hello!
On Wed, Apr 07, 2021 at 03:07:34PM -0700, Demitrious Kelly wrote:
> Given the following two location configurations:
>
> location ~ ^/test/named/(?.+)$ {
> return 200 $foo;
> }
>
> location ~ ^/test/numbered/(.+)$ {
> set $foo $1;
> return 200 $foo;
> }
> Are the following two resu
Hello,
Given the following two location configurations:
location ~ ^/test/named/(?.+)$ {
return 200 $foo;
}
location ~ ^/test/numbered/(.+)$ {
set $foo $1;
return 200 $foo;
}
Are the following two results expected?
# curl http://127.0.0.1:8088/test/named/%D7%94%D7%98%D7%99%D7%95%D7%9C
הטי
