Open hazcod opened 4 years ago
Yes, I know. MITM does not use connection pooling, and I am still considering a solution.
The tunnel agent has used the connection pool.
the reason for the TLS handshake
should be that you did not reuse the connection for each request.
You need to pay attention to:
The client needs to reuse the connection every time it initiates a http request. Otherwise the http request will re-create the connection, resulting in repeated TLS handshake
Hi @telanflow , i'll check the http protocol version. So what does this todo refer to then? https://github.com/telanflow/mps/blob/master/mitm_handler.go#L134
@telanflow Interesting, I've disabled connection: close
on request & response and always use HTTP/1.1
.
Hi, just to let you know that when using
mitmHandler
, a lot of CPU time is spent inmitm_handler.transmit
.Not sure if the client-side connections are pooled?