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
URL encoded path not usable in Dynamic Routing policy #9107
Labels
Projects
Comments
gaetanmaisse
added a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Jul 3, 2023
gaetanmaisse
added a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Jul 3, 2023
mergify bot
pushed a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Jul 3, 2023
https://gravitee.atlassian.net/browse/APIM-2103 gravitee-io/issues#9107 (cherry picked from commit 2f01bfb) # Conflicts: # gravitee-apim-distribution/pom.xml
mergify bot
pushed a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Jul 3, 2023
mergify bot
pushed a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Jul 3, 2023
gaetanmaisse
added a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Jul 3, 2023
gaetanmaisse
added a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Jul 3, 2023
gaetanmaisse
added a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Jul 3, 2023
gaetanmaisse
added a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Jul 4, 2023
gaetanmaisse
added a commit
to gravitee-io/gravitee-api-management
that referenced
this issue
Jul 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug :
Reproduced with the attached API.
What is happening?
Using the Dynamic Routing policy, to redirect to an endpoint if the defined condition is met.
Use the request pathInfo as match expression, which is basically the path called.
When there are encoded characters in the path, the match expression is decoded (here the encoded value %23 is replaced by #). This is causing the issue, because the expression will never match.
A quick workaround could be to replace the encoded value: {#request.pathInfo.replace('%23', '#')}
tested in 3.18.20
Attachments
API-Echo-1 (2).json
* Please see Zendesk Support tab for further comments and attachments.
The text was updated successfully, but these errors were encountered: