On Wed, 23 Nov 2005, Gonzalo Arana wrote:
I would like to add internal redirection support for squid. There is
a patch (see: http://www.squid-cache.org/bugs/show_bug.cgi?id=1208).
Interesting.
Would be better to have this moved to devel.squid-cache.org until it can
be merged, only using the bugzilla to keep track of status.
Henrik suggested in that the core access controls should be reworked.
Yes.. the current allow/deny only result is somewhat limiting when trying
to apply acl processing on anything elese than http_access. Need a more
general "action" concept as result...
directive action acl...
for http_access the only actions today are accept/deny, but I could see a
couple of additional desireable actions there...
reset: deny, but just send a tcp reset, no error message
redirect url: Redirect the client to the given URL
Then there is some intersting new directives which could be built using
this construct. For example forwarding selection in a more logical manner
than todays mess of always_direct,never_direct,cache_peer_access etc.
forward direct acl...
forward peergroup acl...
forward peername acl...
processed in top-down manner.
Delay pool selection could also benefit greatly from this
delay poolnumber acl...
delay poolnumber acl...
And then there is access_log, already using a similar logics but in a very
"raw" manner.
Regards
Henrik
