Huh okay, looks like maybe the `protocol-http` or `protocol-http2` gem made non-backwards-compatible changes that broke `async-http`. But moving to the very latest `async-http` seems to fix it. Okay! |
||
|---|---|---|
| .. | ||
| cache | ||
| javascript | ||
Huh okay, looks like maybe the `protocol-http` or `protocol-http2` gem made non-backwards-compatible changes that broke `async-http`. But moving to the very latest `async-http` seems to fix it. Okay! |
||
|---|---|---|
| .. | ||
| cache | ||
| javascript | ||