On June 9, 2011 11:43:31 AM Leif Hedstrom wrote: > I have no idea, this is something amc will have to take a look at. But, > as far as I know, the idea was to make tproxy works basically the same > as Squid does.
Squid has WCCP/WCCP2/Transparent/Tproxy modes. According to Squid at least, they are all different. But good news... I have ATS (apparently) using Tproxy and it is definitely taking requests from my web browser through L4 redirections. However, it isn't actually working because I see this in my logs: 20110609.11h45m21s CONNECT: could not connect to 72.26.207.52 for 'http://www.alternet.org/' (setting last failure time) 20110609.11h45m21s RESPONSE: sent 199.246.2.116 status 502 (Connect Error <internal error - server connection terminated/-19999>) for 'http:///' And in the browser: internal error - server connection terminated While the list response times are usually not long, I think I will backtrack a bit and see if I can find anything obviously wrong... I think I may have turned reverse_proxy back on because of a random note, will try without, etc. etc. and report. Conversely, it *may* be that my testbed box is using only one ethernet port and tproxy rules may be stomping on the box's ability to connect outwards on port 80. Will go down that avenue as well, although I would rather not have to use two ports on the production boxes since I have the current ones wired directly (no switch) for HTCP and would do ATS clustering that way by preference as well.
