Wrong parsing of short path arguments with symbols that should be escaped

I have endpoints look like `http://127.0.0.1:3050/smth1/{arg1}/smth2/{arg2})`
If you want to have `arg1=.` and pass it through web form, the generated URL looks like
`curl --request GET --url http://127.0.0.1:3050/smth1/smth2/{arg2}`, so it just cuts this argument.
The same behaviour if I put `%2E` (escaped dot) as the parameter.
So, I can't pass the dot as the argument through the web page at all.