Thursday, June 15, 2006

URL Paths 2

From the comments of my original post about URL Paths:

<qoute src="Jon Cavallo">
You can put *.com in the URL Paths. You need to enter it as '/*.com'

I use the /*.x convention on all my extension blocking. This helps prevent them from wildcarding some other part of a complex url.
</quote>

You are totally right, this is a better way to implement extension blocking with URL Paths. Thanks

4 Comments:

Blogger ed said...

Could I have an example please of the use of this? I am still confused in the wording. Thanks!
Great SITE!

9:37 PM  
Blogger Placebo said...

Open the Fireware Policy Manager --> Setup -> Actions --> Proxies... --> select the proxy you are using. --> Edit --> HTTP Request --> URL Path's --> Set 'If matched' to Deny --> Enter a extension you want to block in the 'Pattern:' box and click add.
If you want to block *.pif files enter

*/*.pif

Is a client then request http://evil-website.org/evil.pif it will be denied.

The fist * will match evil-website.org
the / will match /
The second * will match evil
and .pif will match .pif

11:26 PM  
Blogger Placebo said...

If you are becomming more familiar with the software you can also take a look at

http://watchguardtricks.blogspot.com/2006/02/body-content-type-rules.html

The Body Content Type's option does not check the url but the file itself. This means that If I rename my evil.exe to evil.gif it will still be denied as a executable.

11:32 PM  
Blogger ed said...

Thanks for the explanation and tips!

4:49 PM  

Post a Comment

<< Home