On Mar 28, 2013, at 4:57 AM, jbd <[email protected]> wrote: > Hi, > >> Well, if you don't change the blacklist often, then just generate a >> remap.config and reload on the live system with traffic_line -x. The >> lookup on the "host" in remap.config is a hash, so it should be good >> performance for many thousands of rules. > > Thank you for the feedback. I've just add a look to the adult category of my > blacklist, it contains 1 million items, not 1000. :D > >> Writing a plugin that uses some sort of database for doing the blacklist >> would not be difficult. > > Yes, shouldn't be too difficult, but I was curious about user experience in > managing blacklist in ATS. Does not seem that there is a lot of forward mode > users =)
I wonder if you could use the authproxy plugin for this? authproxy is a generic way to submit a HTTP request to a helper service who can decide whether the request should be allowed. Possibly, the blacklist could be in the helper service and authproxy could do the Traffic Server integration ... J
