Closed
Bug 1754740
Opened 3 years ago
Closed 2 years ago
Can we simplify TLSFilterTransaction - it does not need to be a nsAHttpTransaction
Categories
(Core :: Networking: HTTP, task, P2)
Core
Networking: HTTP
Tracking
()
RESOLVED
INVALID
People
(Reporter: dragana, Unassigned)
Details
(Whiteboard: [necko-triaged])
This class adds an additional TLS layer for the connection to the origin through a tunnel.
Currently, it is made as a layer between nsHttpTransaction and nsHttpConnection, therefore it implements nsAHttpTransaction. I think this is not necessary and it is complicated.
We should try to make it a layer between nsHttpConnection and the socket. The other option is to make it a part of nsHttpConnection. In that case, the nsHttpConnection will move the transaction data through TLSFilterTransaction before sending it to the socket.
|
Reporter | |
Comment 1•2 years ago
|
||
I have created another bug with a concrete solution.
You need to log in
before you can comment on or make changes to this bug.
Description
•