Re[2]: I need something like ssh -D, but http proxy, not socks

[Ilya Basin]

GC> What about stunnel? http://www.stunnel.org/
Wrong again. Those who understood the question suggest proxy chaining,
although it's not ideal. For example, I need server names to be
resolved on SSH server. The SSH protocol itself supports names
resolving on server (PuTTY is the proof), but ssh -D provides only
socks4, which doesn't support names resolving on server.

Another problem is: we have some applets on remote web sites, and they
refuse to load if I use socks server.

Here's a diagram. Hope it not wraps.

___________________________________________________________________________________________
| _________________________ |
| | private network | |
| | ______________ | |
| ________________ | ----->| ___site 1___ | | |
| | | | | ||java applets|| | |
| | web browser |__ __________ | | -------------- | |
| | _____________ | |->|http proxy| | | ______________ | |
| | | java plugin |___| | + | _____|__|_ | ___site 2___ | | |
| | |_____________|| |ssh client|---(internet)--->|ssh server|-->||java applets|| | |
| | | ---------- |__________| -------------- | |
| |________________| | | ... | |
| | | ______________ | |
| | ----->| site n | | |
| | -------------- | |
| |_________________________| |
| |
| __________________________________________________________________________________________|

[Bryan Harris]

I bet you have a setting problem.

Firefox doesn't tunnel DNS over socks by default.  Go to
"about:config" in firefox and search for
"network.proxy.socks_remote_dns", and set this to "true".

Then, it should just work.  An applet shouldn't know it's tunneled.
Bryan