Open
Bug 1754734
Opened 3 years ago
Updated 1 year ago
Improve testing of the proxy code
Categories
(Core :: Networking: Proxy, task, P2)
Core
Networking: Proxy
Tracking
()
NEW
People
(Reporter: dragana, Unassigned)
References
(Depends on 3 open bugs, Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
We have a lot of servers and proxies in tests already, but they do not cover all scenarios and are hard to use. The main idea of this meta bug is to fill the gap and also make it easy to set up for a test. Ideally, we want one function call with a configuration that sets up everything.
- Servers:
- A server that fails TLS handshake (this one will be used for a proxy as well). We have some, but we need to extend it and make it easier to use.
- Secure HTTP/1.1 - We have at least 2 versions, but it needs to be improved, e.g. to test session tickets, etc,
- HTTP/2 - We have one, but needs to be improved, e.g. stream limits, session tickets, etc.
- Proxies:
- HTTP/1.1 - We can mimic one with our HTTP/1.1 server, but some scenarios are not possible at the moment, e.g. an HTTP/2 over an HTTP/1.1 proxy.
- A proxy that fails a TLS handshake - the same as a server, see above.
- Secure HTTP/1.1
- HTTP/2 - We have one, but it needs to be extended, e.g. an HTTP/2 over an HTTP/2 proxy.
Reporter | ||
Updated•3 years ago
|
Summary: Improve testing of the proxy code → [meta] Improve testing of the proxy code
Comment 1•1 year ago
|
||
Moving bug to Core/Networking: Proxy.
Component: Networking: HTTP → Networking: Proxy
Updated•1 year ago
|
Keywords: meta
Summary: [meta] Improve testing of the proxy code → Improve testing of the proxy code
You need to log in
before you can comment on or make changes to this bug.
Description
•