Skip to content
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

Ensure Iterable values are encoded before template expansion #1138

Merged
merged 6 commits into from Dec 27, 2019

Conversation

kdavisk6
Copy link
Member

@kdavisk6 kdavisk6 commented Dec 26, 2019

Fixes #1123, Fixes #1133, Fixes #1102, Fixes #1028, Fixes #1096, Fixes #1087, Fixes #1064

Ensures that all expressions are fully-encoded before being
manipulated during template expansion. This allows parameters
to include reserved values and result in properly encoded
results.

Additionally, Iterable values are now handled in accordance
with RFC 6570 allowing for the specified CollectionFormat to
be applied and empty parameters to be expanded correctly as this
is the main use case that exhibited this issue.

Fixes OpenFeign#1123, Fixes OpenFeign#1133, Fixes OpenFeign#1102, Fixes OpenFeign#1028

Ensures that all expressions are fully-encoded before being
manipulated during template expansion.  This allows parameters
to include reserved values and result in properly encoded
results.

Additionally, `Iterable` values are now handled in accordance
with RFC 6570 allowing for the specified `CollectionFormat` to
be applied and empty parameters to be expanded correctly as this
is the main use case that exhibited this issue.
kdavisk6 and others added 5 commits December 27, 2019 08:47
…gn#1140)

* Ensure all brackets are decoded in JSON based Body Templates

Fixes OpenFeign#1129

When JSON is detected in a Body Template, all start and end tokens
that may have been pct-encoded are decoded, ensuring that the
expanded result is valid JSON.
Fixes OpenFeign#1036

Relaxed the regular expression used to determine if an expression
is valid to support additional expression variable names.  We will
no longer restrict what an expression name can be.
Fixes OpenFeign#1123, Fixes OpenFeign#1133, Fixes OpenFeign#1102, Fixes OpenFeign#1028

Ensures that all expressions are fully-encoded before being
manipulated during template expansion.  This allows parameters
to include reserved values and result in properly encoded
results.

Additionally, `Iterable` values are now handled in accordance
with RFC 6570 allowing for the specified `CollectionFormat` to
be applied and empty parameters to be expanded correctly as this
is the main use case that exhibited this issue.
@kdavisk6 kdavisk6 merged commit a7b7c01 into OpenFeign:master Dec 27, 2019
@kdavisk6 kdavisk6 deleted the gh-1123-correct-list-expansion branch December 27, 2019 15:26
@kdavisk6 kdavisk6 added this to the 10.7.1 milestone Dec 27, 2019
kdavisk6 added a commit to kdavisk6/feign that referenced this pull request Jan 17, 2020
Fixes OpenFeign#1156

Collection Format was encoding query string values unnecessarily
due to changes introduced in OpenFeign#1138 and OpenFeign#1139 that encode template
values before appending them to the query string.

In addition, `decodeSlash` flags that were accidentally removed,
have been restored in QueryTemplate.
kdavisk6 added a commit to kdavisk6/feign that referenced this pull request Jan 18, 2020
Fixes OpenFeign#1156

Collection Format was encoding query string values unnecessarily
due to changes introduced in OpenFeign#1138 and OpenFeign#1139 that encode template
values before appending them to the query string.

In addition, `decodeSlash` flags that were accidentally removed,
have been restored in QueryTemplate.
kdavisk6 added a commit that referenced this pull request Jan 18, 2020
Fixes #1156

Collection Format was encoding query string values unnecessarily
due to changes introduced in #1138 and #1139 that encode template
values before appending them to the query string.

In addition, `decodeSlash` flags that were accidentally removed,
have been restored in QueryTemplate.

* Restoring decodeSlash in QueryTemplate

* Correcting Readme with regards to decodeSlash usage
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unexpected or incorrect behavior
Projects
None yet
1 participant