On Tue, 23 Nov 2010 14:49:03 -0600, Dan Johansson <djohansson@xxxxxxxxxxxxx> wrote: >> On 11/22/2010 06:27 PM, Amos Jeffries wrote: >>> eCAP could do it as a workaround. Technically with squid focus on not >>> altering requests itself this is theoretically the correct way to do it. >>> >>> long-term plans are to port location_rewrite eventually unless someone >>> comes up with a fast eCAP plugin for it. >> >> Can eCAP intercept 30x redirects? I have worked with ICAP and as far >> as I could tell, that did not intercept 30x redirect responses (maybe >> I missed something?). If it does I could certainly see it working, and >> something that would be much easier to implement and maintain. >> > As a followup it appear that I did miss something. ICAP does indeed > handle 30x redirects, for some reason I couldnt figure it out before. > Anyway, it will work for what we need, it wont be as high performance as > having a module built into squid. *e*CAP would be better. It is loaded internal to Squid fro better performance and can be plugged into an c-icap server if needed separately. Amos
