You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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
The text was updated successfully, but these errors were encountered: