HoneyryderChuck a03e93e531 allow for oportunistic upgrades, such as the apache Upgrade: h2 ...

this is achieved by a rework of the upgrade plugin, and the addition of
an h2 upgrade plugin. The idea is the following: if a response carries
an Upgrade header, and there's a handler for it, we should go for it.
The difference is:

* when the response is 101, this means that the negotiation must take
  place before the actual response comes in;
* when the response is 200, upgrading means reconnecting to the channel,
  and assume the new protocol for subsequent requests only.

2021-03-05 12:23:17 +00:00

..

authentication.rb

added tests for aws sigv4

2021-02-02 18:33:24 +00:00

aws_authentication.rb

waiting for localstack to be up before running the tests in CI

2021-02-06 16:24:35 +00:00

compression.rb

regression test for bug fixed in 0.11.3

2021-02-17 00:55:05 +00:00

cookies.rb

regression test for issue fixed in v0.11.2

2021-02-17 01:23:16 +00:00

expect.rb

added a global store for domains not supporting 100-continue

2021-01-12 23:53:18 +00:00

follow_redirects.rb

verifyig error responses annd deltas using internal methods

2021-01-05 18:57:39 +00:00

h2c.rb

added (and fixing bug for) test of subsequent request on upgraded

2021-03-05 12:23:07 +00:00

multipart.rb

more explicit error message in multipart test

2021-02-16 18:27:05 +00:00

persistent.rb

added explicit response closing in tests

2020-11-22 15:55:43 +00:00

proxy.rb

socks5 test covering failed authenticationn path

2021-01-14 00:35:22 +00:00

push_promise.rb

enable push frames in no push test in order to force refusal

2021-01-14 00:34:51 +00:00

rate_limiter.rb

supporting the retry-after header for redirections as well

2020-10-31 14:15:28 +00:00

retries.rb

verifyig error responses annd deltas using internal methods

2021-01-05 18:57:39 +00:00

stream.rb

fixing log_exception signature

2020-11-24 16:38:46 +00:00

upgrade.rb

allow for oportunistic upgrades, such as the apache Upgrade: h2

2021-03-05 12:23:17 +00:00