From: Eliezer Croitoru <eliezer@xxxxxxxxxxxx> To: squid-users@xxxxxxxxxxxxxxx Cc: Sent: Saturday, July 28, 2012 10:53 AM Subject: Re: tproxy can't connect to target url after url rewrite program to different host On 07/28/2012 02:55 AM, Ming-Ching Tiew wrote: >> >> Tested this with Squid Version 3.1.20-20120710-r10457, >> >> After a simple url_rewrite_program changing from url to >> a different host, the communication will not succeed >> ( using linux bridge with ebtables/iptables for this tproxy >> >> communication ). >> >> The nat intercept mode could succeed. >only for the url? >for me it works fine. Further testing revealed that if the re-written url is at port 80, then it works. If the url is changed to a different port, then it will timeout. Eg http://dfsdffsa:8080/fsdafsdf Looks like there is a restriction here, because when squid opens a connection faking the client (tproxy), the reply since is it not port 80, it is not coming back to squid.
