-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
In spring cloud gateway mvc, an exception occurs when the request address contains spaces #3185
Comments
In the future, please paste text rather than screenshots. How are you accessing that URL? Through a browser it automatically URL encodes it. |
@spencergibb |
Replacing spaces Maybe @rstoyanchev might have an opinion? |
Hi, we're facing issues with all encoded characters in query parameters. like the norwegian Flipping the Stack trace as text:
|
@spencergibb @rstoyanchev |
@tomgag |
By holding our change. We own both sides, so might rewrite this to a POST. |
To rewrite the GET request into POST, we need to do a lot of adaptation work, and it does not conform to the style of restful api, so we hope there are other better ways to handle it. |
@spencergibb @rstoyanchev @spring-cloud-issues I think the core cause of this issue is the inconsistent behavior of the queryParam passed in the image below: I hope the official can fix this problem as soon as possible. There has been no progress for three months. |
Same issue with accentuated letters.
|
Describe the bug
Exception occurs when the request address contains spaces: Invalid character ' ' for QUERY_PARAM in "2023-12-11 00:00:00"
Before this, I was using the webflux gateway and this problem did not occur.
Details
spring boot 3.2.0
spring cloud 2023.0.0
spring cloud starter gateway mvc 4.1.0
request url: http://localhost:8080/enterprise-service/api/v3/enterprise?start_created_time=2023-12-11 00:00:00&end_created_time=2023-12-12 00:00:00
I hope your team can help us analyze the possible causes and provide some solutions as soon as possible. Thank you very much!
The text was updated successfully, but these errors were encountered: