On 6/8/06, Proniewski Patrick <patrick.proniewski@xxxxxxxxxxxxx> wrote:
Hi On 8 juin 06, at 15:21, Joshua Slive wrote: >> <LimitExcept GET> >> Deny from env....(BlockBrowser AND BlockReferer) >> Deny from env=BlockCountry >> </LimitExcept> > > BrowserMatch "^$" BlockBrowser=1 > SetEnvIf Referer "^$" BlockReferer=1 > SetEnvIf BlockBrowser ^1$ GoAway > SetEnvIf BlockReferer ^1$ GoAway > Deny from env=GoAway > > But it would be easier just to set the GoAway variable in the original > BrowserMatch/SetEnvIf if you don't need those specific variables > elsewhere. I don't think this can work, if BlockBrowser=1 then you set GoAway, if BlockReferer=1 then you set GoAway. If I deny from env=GoAway, then I deny from BlockBrowser OR from BlockReferer. I want to deny only if both BlockBrowser AND BlockReferer are set. But you give me an idea to work with. I'm going to try: SetEnv GoAway 1 BrowserMatch !"^$" !GoAway SetEnvIf Referer !"^$" !GoAway Deny from env=GoAway So, if I'm correct, GoAway is set, then if BrowserMatch is good GoAway is unset, if SetEnvIf Referer is good GoAway is unset, is GoAway is still set, the deny is triggered. Does it look ok ?
Close. Try: SetEnvIf Request_URI .* GoAway=1 BrowserMatch .+ !GoAway SetEnvIf Referer .+ !GoAway Deny from env=GoAway I use a SetEnvIf that always matches rather than the SetEnv because the latter occurs in a different phase of config processing and therefore won't necessarily work here. I use ".+" to indicate that the User-Agent and Referer must contain at least one character to unset the GoAway. Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|