<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">As far as I know, the tcp proxy module
intends to be a reverse proxy for any tcp connection, while my
SOCKS suggestion would be to support forward proxies in
proxy_pass, uwsgi_pass, fastcgi_pass, etc.<br>
<br>
Tom<br>
<br>
<br>
Op 1/25/13 4:45 AM, 姚伟斌 schreef:<br>
</div>
<blockquote
cite="mid:CAGxuLK1e9hyG_WuB1jj1SHdmfO2WCq0B0sUmrMxLOBbc-Xpjpw@mail.gmail.com"
type="cite">I have no idea about the SOCK4a/SOCK5 protocol. Is it
similar with the tcp proxy module? <a moz-do-not-send="true"
href="https://github.com/yaoweibin/nginx_tcp_proxy_module">https://github.com/yaoweibin/nginx_tcp_proxy_module</a><br>
<br>
<div class="gmail_quote">
2013/1/24 Tom van der Woerdt <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:info@tvdw.eu"
target="_blank">info@tvdw.eu</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
A project I'm working on has a backend server that, for
security reasons, can only be accessed via a SOCKS4a/SOCKS5
proxy. A frontend server for this project (nginx) has one
simple task: to proxy all incoming connections to the backend
server.<br>
<br>
Right now, nginx cannot do this, because it has no support for
proxying upstream connections via a SOCKS proxy. The current
temporary workaround is to run another service on the frontend
machine that acts like a HTTP server but proxies the data to
the backend - basically everything I'd like nginx to do. I
cannot use this service as my main frontend, because there are
a few other files that also need to be served.<br>
<br>
SOCKS4a and SOCKS5 are really easy protocols and are basically
just sockets but with an alternate handshake (skip the DNS
lookup, send the hostname to the socket instead). Since they
should be so easy to implement, I'm requesting that on this
mailing list.<br>
<br>
I was thinking of a config file that would look something like
this :<br>
<br>
upstream backend {<br>
server hidden_dns.local socks4=<a
moz-do-not-send="true" href="http://127.0.0.1:1234"
target="_blank">127.0.0.1:1234</a>;<br>
}<br>
<br>
server {<br>
location / {<br>
proxy_pass <a moz-do-not-send="true"
href="http://backend" target="_blank">http://backend</a>;<br>
}<br>
}<br>
<br>
As far as I'm aware, this feature wouldn't break anything,
since a SOCKS connections behaves just like any other normal
socket.<br>
<br>
Thanks for considering,<br>
Tom van der Woerdt<br>
<br>
<br>
_______________________________________________<br>
nginx-devel mailing list<br>
<a moz-do-not-send="true" href="mailto:nginx-devel@nginx.org"
target="_blank">nginx-devel@nginx.org</a><br>
<a moz-do-not-send="true"
href="http://mailman.nginx.org/mailman/listinfo/nginx-devel"
target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx-devel</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
Weibin Yao<br>
Developer @ Server Platform Team of Taobao
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
nginx-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:nginx-devel@nginx.org">nginx-devel@nginx.org</a>
<a class="moz-txt-link-freetext" href="http://mailman.nginx.org/mailman/listinfo/nginx-devel">http://mailman.nginx.org/mailman/listinfo/nginx-devel</a></pre>
</blockquote>
<br>
</body>
</html>