You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When it comes to HTTP Tunnel , nitmproxy decode the payload of the CONNECT payload , which seems not what a tunnel should do.A tunnel should not case about what was in the payload , In theory , at least in my knowledge.
In this approach , http tunnel is not much different from the http proxy.
Meanwhile , It can not pass the tls check when I try to connect to a https website with http tunnel with curl.
becase whe key it get is from the proxy server , not the origin website we wanna go.
Did you actually add the NITMP proxy cert to your CA store? Generate a certificate, start NITM with a certificate and add the .cer file as a CA cert on your machine. This error should go away. You may be able to provide the self-signed cert directly in curl but read the docs.
When it comes to HTTP Tunnel , nitmproxy decode the payload of the CONNECT payload , which seems not what a tunnel should do.A tunnel should not case about what was in the payload , In theory , at least in my knowledge.
In this approach , http tunnel is not much different from the http proxy.
Meanwhile , It can not pass the tls check when I try to connect to a https website with http tunnel with curl.
becase whe key it get is from the proxy server , not the origin website we wanna go.
correct me if I get it wrony.
thanks.
The text was updated successfully, but these errors were encountered: