spring-cloud / spring-cloud/spring-cloud-gateway
Spring Cloud Gateway not allowing Encoded URL paths after Update
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
Describe the bug
I just updated my Spring Cloud Gateway Application from 2021.0.1 to 2023.0.1 and Spring Boot from 2.7.3 to 3.2.5. I have noticed that URL encoded values (like %2F) returns a HTTP Status 400 – Bad Request. I have tried putting break points but none seem to be hit. Is this no longer supported in the new version or there is a setting I'm missing or it's a bug?
Sample
Calling http://localhost:8080/user/abc%2Fxyz doesn't work but http://localhost:8080/user/abc/xyz and http://localhost:8080/user/abcxyz both work after this change
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by reproducing the reported request behavior with /user/abc%2Fxyz across the listed Spring Cloud Gateway and Spring Boot versions, then trace where the request is rejected; done means determining whether encoded paths are supported and identifying the required fix or configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100