-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Routing does not match url-encoded path #262
Comments
Can you post your code?
…On Sun, May 3, 2020, 6:01 AM PaulRivier ***@***.***> wrote:
Hi there,
I can not find a way to match an URL encoded path such as /page/P%C3%A2tes
It seems to fail with both capture pattern, placeholders and regex.
Is this a bug ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#262>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEOIX25U6EJDA5SMNMRVFPTRPVTLJANCNFSM4MYDXQWA>
.
|
Hello, thank you for your quick reply. I messed my test cases before posting my original message, sorry about that. This is a more proper report, thank you for caring. This works and matches /page/Pâtes
But I need to match the rest of the url after page, not only first segment, so /page/recette/Pâtes would match with path=recette/Pâtes. I could not find a clean way to get this behaviour, so I used the regex feature. My regex is something like :
It does match correctly /page/Hello, but it is buggy on /page/Pâtes. Basically, it will only match "P". Interestingly, if regexp ends with "$" (like "^/page/(.+)$"), it does not match at all accentuated words. Maybe the regex feature has some issues with multibytes chars. I would appreciate a lot to have a pattern to match the remaining of the path, like "/page/:~page" or so. Thank you. |
@PaulRivier url-decoding parameters looks buggy indeed |
As pointed out by @jfraudeau this is indeed fixed by #302 |
Thank you guys.
…On Sun, Dec 17, 2023 at 5:19 PM Marco Z ***@***.***> wrote:
Closed #262 <#262> as
completed.
—
Reply to this email directly, view it on GitHub
<#262 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIT5BNOHCP3YDVI3CBWTAYLYJ4LR5AVCNFSM4MYDXQWKU5DIOJSWCZC7NNSXTWQAEJEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW4OZRGEZDMOBYGU3TGOBZ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi there,
I can not find a way to match an URL encoded path such as
/page/P%C3%A2tes
It seems to fail with both capture pattern, placeholders and regex.
Is this a bug ?
The text was updated successfully, but these errors were encountered: