Skip to content
This repository was archived by the owner on Jan 30, 2020. It is now read-only.

Conversation

@av3
Copy link
Contributor

@av3 av3 commented Feb 14, 2019

As described in #172 there is currently no support for HTTP/2. I tried to fix it on my own and was able to process a HTTP/2 response. Hopefully this PR makes sense; I also added/extended unit tests and the documentation.

samsonasik and others added 4 commits February 15, 2019 01:23
Co-Authored-By: av3 <av3@users.noreply.github.com>
Need to indicate that HTTP/2 support is only available in 2.10.0 and up.
Extracts `validHttpVersions()` and `validResponseHttpVersionProvider()`
methods to ensure we test various functionalities against each of the
three supported HTTP versions.

Updates `testResponseFactoryFromStringCreatesValidResponse()` to use the
latter, and splits `testResponseCanRenderStatusLine()` into
`testResponseCanRenderStatusLineUsingDefaultReasonPhrase()` and
`testResponseCanRenderStatusLineUsingCustomReasonPhrase()`, each using
`validHttpVersions()` as a data provider.
weierophinney added a commit that referenced this pull request Feb 19, 2019
- Updates branch aliases:
  - dev-master => 2.10.x-dev
  - dev-develop => 2.11.x-dev
- Updates CHANGELOG:
  - Moves notes about #173 to 2.10.0 release
  - Sets date for 2.10.0 release
  - Removes empty stub for 2.9.2 release
@av3 av3 deleted the feature/http2-support branch February 19, 2019 18:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants