-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
fix(core) stop percent decoding regex path #9024
Conversation
Percent decoding of |
A tricky problem: We need a "back migration" to change the config back to 2.8 formats. It's safe to leave most of the characters not changed (and we can not tell if they are not from origin config but decoded in migration). The only character that may cause problems is "%", and it may be double |
18f26ff
to
0c57db4
Compare
0c57db4
to
9fb82ce
Compare
e15a692
to
14084ec
Compare
I've tested migration in my local env and it works as expected. |
It's not a very reliable and sound way to support percent encoding in regex. We choose to tell users that we have a normalized (standard) form to match with so there's no ambiguity. fix CT-344
4bb71f0
to
e736b5c
Compare
It's not a very reliable and sound way to support percent-encoding in regex. We choose to tell users that we have a normalized (standard) form to match with so there's no ambiguity.
#8140 (comment)
fix CT-344