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

Using Protocol.name when resolving HTTP protocol for responses #2428

Merged

Conversation

steam0
Copy link
Contributor

@steam0 steam0 commented May 21, 2024

The toString() method on OkHttp3.Protocol does not return a value that can be used to resolve to enum ProtocolVersion.

This change extracts the name from the Protocol and uses that instead of the whole Protocol object.

Fixes #2427

The `toString()` method on `OkHttp3.Protocol` does not return
a value that can be used to resolve to enum `ProtocolVersion`.

This change extracts the `name` from the Protocol and uses
that instead of the whole Protocol object.

Fixes OpenFeign#2427
@velo velo merged commit d851bf2 into OpenFeign:master May 23, 2024
3 checks passed
@steam0
Copy link
Contributor Author

steam0 commented May 24, 2024

@velo, thanks for the merge. When do you expect that the next version will be released?

@steam0 steam0 deleted the Correctly-resolving-http-response-protocol branch May 27, 2024 05:12
velo pushed a commit that referenced this pull request Oct 7, 2024
The `toString()` method on `OkHttp3.Protocol` does not return
a value that can be used to resolve to enum `ProtocolVersion`.

This change extracts the `name` from the Protocol and uses
that instead of the whole Protocol object.

Fixes #2427

Co-authored-by: Henrik Stene <[email protected]>
velo pushed a commit that referenced this pull request Oct 8, 2024
The `toString()` method on `OkHttp3.Protocol` does not return
a value that can be used to resolve to enum `ProtocolVersion`.

This change extracts the `name` from the Protocol and uses
that instead of the whole Protocol object.

Fixes #2427

Co-authored-by: Henrik Stene <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants