Thanks Alex. We are in a stage where even ICAP cannot be deployed :( So i had started digging into SQUID code to find where hooks can be placed. I was trying to do the following: 1. Configured and ACL (whiteLst) in squid.conf for the allowed list of file. 2. In code i am trying to find a place where it says that url abc,com matches ACL (whiteLst) specified in conf file. If the ACL name matches to whiteLst, i will call a function to add a custom header. I have not been able to find such a place in the code as of yet where i can safely say that my ACL (whiteLst) match has happened. Found a code where "ACLMatchedList" is populated, but on debugging it seems to be generally populated with ACL "ALL". Not sure where the "ALL" acl is being picked up. Some "indent_*" acl is being matched. Even tried with enabling debug logs for squid. Seems it matches the ACL (whiteLst) but then also matches some ACL "ALL", hence overwriting the Matched ACL name. Still debugging, though some pointers or inputs would be welcome here. Thanks in Adv. Regards On Wed, Sep 18, 2013 at 9:41 PM, Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > On 09/17/2013 09:48 PM, Sachin Gupta wrote: > >> We are using Squid 3.1 and need to do the following: >> 1. We have a list of URLs which we want to allow. >> 2. Squid to read this list of URLs and for each matching entry in the >> list, set a particular field (insert a string) in the HTTP header. >> 3. Using this header string, a URL filtering program will allow the >> URLs to be accessed. >> >> I explored the squid functionality and came across following: >> a. header_replace : Not sure how i can use this for my case. Examples >> and references are welcome. >> b. request_header_replace: Not available in 3.1. Not possible to >> upgrade to latest squid release. >> >> Is there any other option to do the same? Please suggest. > > > If Squid upgrade is not an option, you can either modify your Squid > sources or use eCAP/ICAP to do the adaptations you need. > > > > HTH, > > Alex. >
