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

HTTP protocol implementation: allow to configure which protocol version(s) to use #827

Closed
sebastian-nagel opened this issue Oct 5, 2020 · 1 comment

Comments

@sebastian-nagel
Copy link
Contributor

It should be possible to configure which HTTP protocol versions (HTTP/1.1, HTTP/2, etc.) are used by a protocol implementation:

@sebastian-nagel sebastian-nagel added this to the 1.18 milestone Oct 5, 2020
sebastian-nagel added a commit to sebastian-nagel/storm-crawler that referenced this issue Oct 5, 2020
…on(s) to use

implements apache#827
- configuration key `http.protocol.versions` holds a list of protocols
  in order of preference
- implement selection of protocols in okhttp protocol implementation
- fix loading of YAML lists when configuration isn't loaded via Storm
  (eg. by main method of AbstractHttpProtocol)
sebastian-nagel added a commit to sebastian-nagel/storm-crawler that referenced this issue Oct 5, 2020
…on(s) to use

implements apache#827
- configuration key `http.protocol.versions` holds a list of protocols
  in order of preference
- implement selection of protocols in okhttp protocol implementation
- fix loading of YAML lists when configuration isn't loaded via Storm
  (eg. by main method of AbstractHttpProtocol)
jnioche pushed a commit that referenced this issue Oct 6, 2020
…on(s) to use (#829)

implements #827
- configuration key `http.protocol.versions` holds a list of protocols
  in order of preference
- implement selection of protocols in okhttp protocol implementation
- fix loading of YAML lists when configuration isn't loaded via Storm
  (eg. by main method of AbstractHttpProtocol)
@jnioche
Copy link
Contributor

jnioche commented Oct 6, 2020

fixed in #829

@jnioche jnioche closed this as completed Oct 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants