-
### Area of Improvement
When choosing HTTP/1.1 HTTP for your client library, the example code provided for the endpoints starts with "POST /v7/getAppInfo 1.1", which is invalid and should read "POST …
-
### Version
v22.9.0
### Platform
```text
Microsoft Windows NT 10.0.19045.0 x64
```
### Subsystem
node:http2
### What steps will reproduce the bug?
http1.1 requests made from […
-
### Version
v20.17.0
### Platform
```text
MacOS Sonoma 14.5, 2,3 GHz Quad-Core Intel Core i7
```
### Subsystem
_No response_
### What steps will reproduce the bug?
Define an h…
-
*Title*: *HTTP 1.0 / 1.1 : implementation of RFC 2145*
*Description*:
According to nginx behaviour and RFC 2145. See this [link](https://serverfault.com/questions/442960/nginx-ignoring-clients-ht…
-
While attempting to use `async-http` (0.71.0) with against a reverse proxy where we need to specify a `Host` header, the library sends the header twice: one with the URL's hostname value, and one with…
-
low priority and doesn't fit with the original project goal, also risks adding some bloat, but that should be manageable. Still might be nice to have and make this project more "batteries included".…
-
### Existing Issue or Pull Request Verification
- [X] Confirmed, no existing Issues or Pull Requests found related to my submission.
### Package Version
3.2.0
### Are you using the latest version?…
-
### Version
4.5.10
### Context
There appears to be a regression of #3249 . When the connection is closed in the connection handler, the request continues to be dispatched to the request handl…
-
When receiving a response with a header that is folded over multiple lines, the following error is returned:
```
Protocol::HTTP1::BadHeader: Could not parse header
```
I first noticed this iss…
-