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 capture example will be made to work the same as named does?

Cheers!
DK

> Begin forwarded message:
>
> From: Maxim Dounin <mdounin@mdounin.ru>
> 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 wrote:
>
>> Given the following two location configurations:
>>
>> location ~ ^/test/named/(?<foo>.+)$ {
>> 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
>> הטיול
>>
>> # curl http://127.0.0.1:8088/test/numbered/%D7%94%D7%98%D7%99%D7%95%D7%9C
>> %D7%94%D7%98%D7%99%D7%95%D7%9C
>>
>> I have not been able do find any documentation, yet, explaining why these two methods of capturing the same data yield different results.
>
> It's a bug, see https://trac.nginx.org/nginx/ticket/348 https://trac.nginx.org/nginx/ticket/348.
>
> --
> Maxim Dounin
> http://mdounin.ru/ http://mdounin.ru/
> _______________________________________________
> nginx mailing list
> nginx@nginx.org <mailto:nginx@nginx.org>
> http://mailman.nginx.org/mailman/listinfo/nginx http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx