-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
【Help】【H2】 manany request is pending #2503
Comments
Hm, strange. It's "pending" even though you've received the headers? Do they not include a status code? They probably do... How are you using hyper and h2? What version are you using, and how are you configuring the server? |
I use the hyper server to receive the request from the browser and then forward the request to the backend service through the hyper client according to internal rules. If all use HTTP1/1, not found a large number of pending requests. However, when H2 is used from the browser to the hyper server and Http1/1 is used from the hyper client to the backend service, a large number of pending requests occasionally occur. Hyper 0.13.7 tokio-rustls 0.13.1 tokio 0.2.13 configuring like that
|
Firefox also has this problem. |
Are all the requests using the same connection, or are they using different connections? |
same connection, connection id is same |
I've updated with more information on this issue at hyperium/h2#573 |
@seanmonstar Can you help me see if my tests and guesses are correct? |
It's a problem in H2, and I'm going to close the hyper issue. |
We use Hyper + Rustls to develop a proxy service as the entrance to the website. After H2 is enabled for the proxy service (other backend services do not enable H2), there is a possibility that a large number of pending pages may be generated. You must close all tabs of the browser before you can access it again. Strangely, the response header has been received in the pending request. When H2 is not enabled, there is no large number of pending requests.
Only these are the exception logs.:
[2021-04-15 22:06:13 WARN hyper::proto::h2 63] Connection header illegal in HTTP/2: connection
[2021-04-15 22:06:13 WARN hyper::proto::h2 63] Connection header illegal in HTTP/2: connection
[2021-04-15 22:06:13 WARN hyper::proto::h2 63] Connection header illegal in HTTP/2: connection
[2021-04-15 22:07:12 WARN hyper::proto::h2 45] Connection header illegal in HTTP/2: keep-alive
[2021-04-15 22:07:12 WARN hyper::proto::h2 63] Connection header illegal in HTTP/2: connection
The text was updated successfully, but these errors were encountered: