Code: Select all
http://m.[a-z][a-z].2mdn.net/
Code: Select all
http://m.uk.2mdn.net/
Code: Select all
http://m.[a-z][a-z].2mdn.net/
Code: Select all
http://m.uk.2mdn.net/
Code: Select all
/^http:\/\/m\.[a-z][a-z]\.2mdn\.net\//
Okay, thanks. I did not know that.Wladimir Palant wrote:For character classes you have to use regular expressions, simple filters only support * as a wildcard. The regular expression in that case would be:However, I would recommend multiple filters like "http://m.uk.2mdn.net/" and "http://m.us.2mdn.net/" instead - these work a lot faster (even if you add a hundred of them instead of one regular expression).Code: Select all
/^http:\/\/m\.[a-z][a-z]\.2mdn\.net\//
IMO, it's much easier to use a wildcard in this case:Decebal wrote:It is clearer and new links are automatically taken care off. (In my case it is about uk and fr.)
Code: Select all
http://m.*.2mdn.net/
Code: Select all
.2mdn.net/
Your wildcard is much better yes. Also, if it is only an adserver, then the second solution is even better.Ares2 wrote:IMO, it's much easier to use a wildcard in this case:Decebal wrote:It is clearer and new links are automatically taken care off. (In my case it is about uk and fr.)or - as this is a well known adserver - you can block the whole thing:Code: Select all
http://m.*.2mdn.net/
This will definitely take care of new links.Code: Select all
.2mdn.net/
Ath the moment I have 18 filters and one regular expression. So that should not be an problem.Wladimir Palant wrote:Depends on how many regular expressions you get - 40 already create a noticeable delay (on the other hand, 40000 simple filters don't).