B bacanak Member Jul 4, 2005 #1 Jul 4, 2005 #1 I searched the forum but could not find any info I wanna Block "Attacker" from accesing my server all headers with " attacker" should be dropped please advice thnx
I searched the forum but could not find any info I wanna Block "Attacker" from accesing my server all headers with " attacker" should be dropped please advice thnx
M mistwang LiteSpeed Staff Jul 4, 2005 #2 Jul 4, 2005 #2 Please use URL rewrite for now, Apache compatible BrowserMatch will be added soon.
B brrr Well-Known Member Jun 30, 2008 #3 Jun 30, 2008 #3 mistwang said: Please use URL rewrite for now, Apache compatible BrowserMatch will be added soon. Click to expand... Bump. Has this feature arrived? I can't find it. If it never arrived, what would a v3.3.14 Request Filter rule look like that, for example, performed the same as the following in an Apache http.conf: Code: BrowserMatchNoCase ^Jakarta badbot <Files *> Order Allow,Deny Allow from all Deny from env=badbot </Files> ?
mistwang said: Please use URL rewrite for now, Apache compatible BrowserMatch will be added soon. Click to expand... Bump. Has this feature arrived? I can't find it. If it never arrived, what would a v3.3.14 Request Filter rule look like that, for example, performed the same as the following in an Apache http.conf: Code: BrowserMatchNoCase ^Jakarta badbot <Files *> Order Allow,Deny Allow from all Deny from env=badbot </Files> ?
B brrr Well-Known Member Jun 30, 2008 #4 Jun 30, 2008 #4 Sorry - should have searched forum: request filter rule answered here: http://www.litespeedtech.com/support/forum/showthread.php?t=1618&highlight=request+filter Example Request Filter rule: Code: SecFilterSelective HEADER_USER_AGENT ^Jakarta Checked and working. Last edited: Jun 30, 2008
Sorry - should have searched forum: request filter rule answered here: http://www.litespeedtech.com/support/forum/showthread.php?t=1618&highlight=request+filter Example Request Filter rule: Code: SecFilterSelective HEADER_USER_AGENT ^Jakarta Checked and working.
A aww Well-Known Member Aug 14, 2008 #5 Aug 14, 2008 #5 Another vote for BrowserMatch IE8 is going to practically require BrowserMatch to not break existing webpages. Should be simple to impliment no? It's just a matter of testing the requested string against the user-agent?
Another vote for BrowserMatch IE8 is going to practically require BrowserMatch to not break existing webpages. Should be simple to impliment no? It's just a matter of testing the requested string against the user-agent?
M mistwang LiteSpeed Staff Aug 14, 2008 #6 Aug 14, 2008 #6 Since you can implement the same logic with a rewrite rule, we don't see the need for supporting BrowserMatch explicitly.
Since you can implement the same logic with a rewrite rule, we don't see the need for supporting BrowserMatch explicitly.
A aww Well-Known Member Aug 14, 2008 #7 Aug 14, 2008 #7 Remember the idea is to be as completely compatible with existing htaccess files as possible. I want to be able to use something as simple as this: Code: BrowserMatch MSIE ie8-support Header set X-UA-Compatible IE=7 env=ie8-support
Remember the idea is to be as completely compatible with existing htaccess files as possible. I want to be able to use something as simple as this: Code: BrowserMatch MSIE ie8-support Header set X-UA-Compatible IE=7 env=ie8-support