>On Mon, 2003-08-11 at 13:19, Joshua Brindle wrote: >> after trying to use deny_info with my http_reply_access >> acl and being unsuccessful i searched the web and found >> that others had that problem and that it was a known limitation. >> >> My question is, what kind of limitation is it? one where the code >> just hasn't been written or is it a design limitation? (in squid-3) >> >> if it's the former i'll take a shot at writing it, i'd like to know >> before >> i waste a lot of time though.. Thanks > >It -was- both. > >There was a design limitation, that is (IIRC) fully resolved now. > >So, you should be able to factor out, and then reuse the deny info logic >for requests to the appropriate area in client_side_reply.cc. > Where do you suggest this?
Looking at client_side_reply.cc i see access control stuff all over the place, I take it processReplyAccessResult is the place to put it but I'm not quite sure what the acl flow on the reply side is, I'll start messing with this until someone replies and tells me the correct way to do it :) Joshua Brindle
