Redirect usage is not related to the TCP proxy.
Please search for problems in your backend.

TCP proxy can be used for proxying any protocol unless
you need to change the data bytes (alter HTTP headers,
change method etc)

> On 15 Jun 2015, at 08:33, smith <smith.hua@zoom.us> wrote:
>
> Thanks, is this means TCP proxy not suitable for web usage, for web usage may have many redirect usage?
>
> I’m going to use http/https proxy instead
>
> 发件人: nginx-bounces@nginx.org [mailto:nginx-bounces@nginx.org] 代表 ryd994
> 发送时间: 2015年6月15日 4:21
> 收件人: nginx@nginx.org
> 主题: Re: 答复: 答复: nginx plus with ssl on TCP load balance not work
>
> As long as you get something from your backend, I don't see anything could be wrong on the proxy. Backend get the connection, that's all.
>
> I guess it was because your backend get frustrated for all incoming requests being from frontend. HTTP proxy can pass client IP info by "X-Forwarded-For". That doesn't work for TCP proxy.
>
> For testing, I suggest you to start with some basic http service on your backend.
>
> On Sat, Jun 13, 2015 at 8:53 PM huakaibird <nginx-forum@nginx.us> wrote:
>> Any help on this? not working
>>
>> Posted at Nginx Forum: http://forum.nginx.org/read.php?2,259522,259599#msg-259599
>>
>> _______________________________________________
>> nginx mailing list
>> nginx@nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

--
Roman Arutyunyan



_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx