16 ms·

what I meant was a proxy that implements HTTP/1.1 CONNECT and a server behind it like ``` mkfifo /tmp/myfifo cat /tmp/myfifo | nc -l 12345 > /tmp/myfifo ```

by hnav 4mo ago

what I meant was a proxy that implements HTTP/1.1 CONNECT and a server behind it like ``` mkfifo /tmp/myfifo cat /tmp/myfifo | nc -l 12345 > /tmp/myfifo ``` so if you manually type out CONNECT host:12345 HTTP/1.1 host: host:12345 you can see exactly what's happening. To be fair you can hack curl to support that via curl -x proxy:3333 telnet://host:12345 but that's not exactly what you want and requires curl to have been compiled with telnet support.

Bender 4mo ago
Ah, I see what you mean. Aside from putting the proxy into debug logging one would have to use curl -vvv to get similar details but I suppose whatever works best with muscle memory is the right choice and one may not always have access to put the proxy into debug logging. I need to try this with a Squid SSL Bump MitM proxy just dont have one up at the moment. curl -vvv -A Mozilla -H "Accept-Language: en_us" -H "Sec-Fetch-Mode: navigate" --url 'https://nochan.net/.env'