-
Notifications
You must be signed in to change notification settings - Fork 774
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
FeignClient request parameters not encoded as expected #128
Comments
Not sure why an incorrectly formatted date is seen as an enhancement. |
I am wondering as well why the |
I'm afraid I have no firm answer to that. For the life of me, I cannot find the link, but I saw some reference stating that the the query string parameters do not need to be encoded (or at least to the same extent), so I spent quite a bit of time assuming that the However, since you frequently have less control over the services you call than the clients you write to call them, my attention returned to the unexpected differences in the two client side calls. |
Can you try with the latest release and if it still doesnt work provide a sample to reproduce the problem? |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue. |
Just converted some code from using feign directly and I am seeing a difference in the url created that the server is rejecting.
Using feign to define the client:
The date in the request is formatted
?zonedDateTime=2017-09-19T13:08:00.014%2B03:00[Europe/Athens]
Whereas using
@FeignClient
to define it:The date in the request is formatted
?zonedDateTime=2017-09-19T13:08:00.014+03:00[Europe/Athens]
The plus in the offset was encode by feign's
@Param
but not when using@RequestParam
.The text was updated successfully, but these errors were encountered: