On Tue, 28 Jul 2009 09:44:53 -0400, "ADEBAYO, FOLUSO, ATTSI" <fa682m@xxxxxxx> wrote: > Hi Amos, > Thanks for the response. Can you point me in the direction of an > external ACL helper that can help me do this? Look to the source helpers/external_acl/* or package for the helpers available in your Squid. The session helper emulates web browser page sessions. If that is not enough you will need to have one written that does your operations. There are few external ACL helpers available simply because they are custom built to match each network topology and environment they run under. Its going to contain your own local "business logic policy" after all. For example, the ones I use for quota control with my accounting system won't work for you or others etc. Amos > > Thanks > > -----Original Message----- > From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] > Sent: Monday, July 27, 2009 9:11 PM > To: ADEBAYO, FOLUSO, ATTSI > Cc: squid-users@xxxxxxxxxxxxxxx > Subject: Re: Writing Cookies in SQUID > > On Mon, 27 Jul 2009 15:43:54 -0400, "ADEBAYO, FOLUSO, ATTSI" > <fa682m@xxxxxxx> wrote: >> Hi, >> I need to write a cookie variable to a response from a client in >> Squid so that next time a request comes from that client I can take an >> action. Can someone please point me in the direction of where I would >> need to make the changes in Squid 2.6. >> >> thanks > > Clients do not 'response' to Squid. They make requests. The cookie needs > to > be generated against the domain the client requested, and will be passed > publicly to the web server actually generating the response whenever the > client requests that articular domain, not simply in the next request. > > I would suggest instead looking into an external ACL helper that can > track > client IPs and the domains they visit, then do the action based on its > own > tracking state. This is much simpler and does not involve hacking the > web > requests/response being publicly transmitted. Nor hacking the Squid code > to > abuse HTTP. > > Amos
