Open HoodyStiliyan opened 2 years ago
Hey, I kinda understand what you mean but need some clarification and perhaps a better example. Are you asking me to implement TLS session based resumption for reuse (so we don't reuse a handshake) or do you have something else in mind? Your specific example (exposing the underlying network object) won't quite work like the example you provided in practice.
Yes, I wanted to have the option to reuse the TLS connection and send HTTP packets through it without having to essentially make a handshake for each request.
Any work on this?
Description
Basically, for example in nodejs I can make a new tls connection socket, get the alpn protocol the endpoint needs, then make a new http2.connect socket and feed the tls socket to it. Then I can reuse the connection for multiple requests. The problem that your amazing work solves is it lets me spoof the tls fingerprint, but at the cost of not having control over how the packets are sent.
I would like it there to be a way for me to get the connection socket of the request and feed it to my next request so I can reuse it.
An example of the behavior would be:
Issue Type
Feature Request
Operating System
Windows 10, Linux, Mac OS
Node Version
Other
Golang Version
Other
Relevant Log Output
No response