Hi!

On Thu, Feb 4, 2010 at 16:14, Michal Trojnara Michal.Trojnara@mirt.netwrote:

Dmitry Gromov wrote:

It seems like the latest patch to support HTTP Connect proxy is for 4.05 version. Any one knows if it is compatible with the latest version? If not, is there more recent version of the patch?

I also wonder why this never made to the code... Seems like a very useful feature.

Sure it's useful. That's why I implemented this functionality in stunnel 4.15 (released 11 March 2006).

Oh, I see it now, protocol type "connect". I think, this could be explained a bit more clear in the doc that this is HTTP Connect proxy support.

Now, is SOCKS protocol next on Todo list? :)

Best regards, Mike

Thank you very much for a great product, Mike!!

Hi!

On Fri, Feb 5, 2010 at 05:01, Michal Trojnara Michal.Trojnara@mirt.netwrote:

Dmitry Gromov wrote:

...

I think, this could be explained a bit more clear in the doc that this is HTTP Connect proxy support.

I'm not good at writing manuals. Feel free to contribute a clear (but short) description.

Well, this is a bit tough for me too, but I think section "***protocol = proto*" in man page needs a bit more explanation - stunnel behavior is different between connect and, let's say, smtp. As I understand it, connect is used in client mode only. So adding something like: "connect protocol is used in client mode to establish connection via HTTP proxy" should help. People tend to use internet search to find stuff, and as long as you have three keywords "HTTP connect proxy" - it should be easy to recognize this feature correctly.

...

Now, is SOCKS protocol next on Todo list? :)

It's certainly not difficult to implement, but I'm quite busy.

I perfectly understand. Treat it as a feature request. I just think stunnel will benefit from this support, so - whenever you have some time, could you please look into implementing it?

Thanks again, Dmitry