Closed
Bug 1562887
Opened 5 years ago
Closed 5 years ago
Idle h2 proxy tunnels carrying h1 traffic should timeout shortly (similarly to h1 connections)
Categories
(Core :: Networking: HTTP, defect, P3)
Core
Networking: HTTP
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mayhemer, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged][secure-proxy][skyline])
Because otherwise we keep too many open streams and hit bug 1562885.
Reporter | ||
Comment 1•5 years ago
|
||
When the target https server is talking h1 only, this is particularly painful. When there are e.g. 8 requests, 6 go out each on its own tunnel. The other 2 are queued. Then we wait for a tunnel close, not a tunnel becoming idle.
Reporter | ||
Updated•5 years ago
|
Priority: -- → P3
Summary: Unused h2 proxy streams should timeout shortly → Idle h2 proxy tunnels carrying h1 traffic should timeout shortly (similarly to h1 connections)
Updated•5 years ago
|
Whiteboard: [necko-triaged][secure-proxy-skyline]
status-firefox70:
--- → affected
Whiteboard: [necko-triaged][secure-proxy-skyline] → [necko-triaged][secure-proxy][skyline]
Reporter | ||
Comment 2•5 years ago
|
||
There is no need. Parallelism is usually very high. We will queue streams over the limit and after fixing bug 1563027 this will no longer be an issue.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•