Soner Tari

Per README, "For HTTP and HTTPS connections, SSLproxy mangles headers to [...] prevent switching to QUIC/SPDY, HTTP/2 or WebSockets (Upgrade, Alternate Protocols)." So, the answer is no, sorry.

Good question, so I can explain the differences better. SSLproxy is based on SSLsplit, a very nice work by Daniel. With SSLsplit, you can decrypt and view encrypted packets. Great...

Everything between the SSLproxy and the listening program is exchanged in packets over networking sockets (SSLproxy/SSLsplit use bufferevents in libevent, which is responsible for all such lower level details as...

To explain my design decisions further, an important benefit of using packets over networking sockets between the SSLproxy and the listening program is that I use OpenBSD/pf to divert those...

Another good question to explain the details. The critical part is the SSLproxy specific line it inserts into the first packet in the connection. Refer to the README file for...

The points 4 and 5 in [my comment above](https://github.com/sonertari/SSLproxy/issues/1#issuecomment-416398026) explain possible issues with trying to support other protocols (binary, proprietary, or not). You may want to read those points again....

OK, you are right about documentation. I have committed and pushed a new revision which enables SSLproxy header insertion similar to pop3 and smtp for all protocols other than http....

Note: This is a duplicate of a request [here](https://github.com/shaun-lloyd/squid/issues/2) What I understand from your request is that you want to log in to the system only once and be able...

Btw, you may be able to achieve what you want using a TCP proxyspec for SSH connections. So, basically, you will log in to the system only once over HTTP/s,...

First things first: Since you don't mention any listening program and its configuration, I guess you are not running one. You need a listening program for sslproxy to divert the...