-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Body contains % , as JSON, UriUtils.decode error #916
Labels
waiting for feedback
Issues waiting for a response from either to the author or other maintainers
Comments
This was referenced Mar 6, 2019
Can you please provide a test case for this? Data provided either through the |
Data provided the @Body annotations are not encoded. |
kdavisk6
added a commit
to kdavisk6/feign
that referenced
this issue
Mar 27, 2019
Fixes OpenFeign#916 In certain cases, a Body Template will contain a JSON payload. To support this we are asking users to pct-encode the beginning and the end of the JSON object when providing it to the RequestLine so we don't reject it as an expression. Doing this requires that the we decode those markers before submitting the request. This change updates that logic to only decode the first and last characters only and not decode the entire payload, since Body values don't require any type of encoding.
kdavisk6
added a commit
to kdavisk6/feign
that referenced
this issue
Mar 27, 2019
Fixes OpenFeign#916 In certain cases, a Body Template will contain a JSON payload. To support this we are asking users to pct-encode the beginning and the end of the JSON object when providing it to the RequestLine so we don't reject it as an expression. Doing this requires that the we decode those markers before submitting the request. This change updates that logic to only decode the first and last characters only and not decode the entire payload, since Body values don't require any type of encoding.
kdavisk6
added a commit
to kdavisk6/feign
that referenced
this issue
Mar 27, 2019
Fixes OpenFeign#916 In certain cases, a Body Template will contain a JSON payload. To support this we are asking users to pct-encode the beginning and the end of the JSON object when providing it to the RequestLine so we don't reject it as an expression. Doing this requires that the we decode those markers before submitting the request. This change updates that logic to only decode the first and last characters only and not decode the entire payload, since Body values don't require any type of encoding.
kdavisk6
added a commit
that referenced
this issue
Apr 8, 2019
Removed decoding from Body Template Expansion Fixes #916 In certain cases, a Body Template will contain a JSON payload. To support this we are asking users to pct-encode the beginning and the end of the JSON object when providing it to the RequestLine so we don't reject it as an expression. Doing this requires that the we decode those markers before submitting the request. This change updates that logic to only decode the first and last characters only and not decode the entire payload, since Body values don't require any type of encoding.
velo
pushed a commit
that referenced
this issue
Oct 7, 2024
Removed decoding from Body Template Expansion Fixes #916 In certain cases, a Body Template will contain a JSON payload. To support this we are asking users to pct-encode the beginning and the end of the JSON object when providing it to the RequestLine so we don't reject it as an expression. Doing this requires that the we decode those markers before submitting the request. This change updates that logic to only decode the first and last characters only and not decode the entire payload, since Body values don't require any type of encoding.
velo
pushed a commit
that referenced
this issue
Oct 8, 2024
Removed decoding from Body Template Expansion Fixes #916 In certain cases, a Body Template will contain a JSON payload. To support this we are asking users to pct-encode the beginning and the end of the JSON object when providing it to the RequestLine so we don't reject it as an expression. Doing this requires that the we decode those markers before submitting the request. This change updates that logic to only decode the first and last characters only and not decode the entire payload, since Body values don't require any type of encoding.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
waiting for feedback
Issues waiting for a response from either to the author or other maintainers
Request Body
{ "percent" : "100%", "name" : "lee" }
Feign client declarative invocation will decode throw exception
URLDecoder.decode() code
throw new IllegalArgumentException( "URLDecoder: Illegal hex characters in escape " + "(%) pattern - negative value");
UriUtils.decode() should be contain IllegalArgumentException, return the original value .
The text was updated successfully, but these errors were encountered: