topic Re: http-req-uri-path limitation in Automation/API Discussions

http-req-uri-path limitation

Dingo — Sat, 13 Dec 2014 01:05:49 GMT

Does anyone know why there is a 7 character minimum when using "http-req-uri-path"?

How would you block on URI for the follwing example:

http://FQDN.com/abc/dynamicContent01.jsp

I cannot filter on just /abc/ as it expects min 7 characters and dynamicContent01.jsp being a dynamically created extention that is unpredictable.

Re: http-req-uri-path limitation

bat — Sat, 13 Dec 2014 01:07:15 GMT

Hi DavePANOS

For min 7 character limit did you try this: FQDN\.com\/abc\/

Hope it helps !

Re: http-req-uri-path limitation

HITSSEC — Mon, 15 Dec 2014 16:49:37 GMT

Hi DavePANOS

Since the uri path comes after the host name there is the limitation of 7 characters that prevents you in the example shown. One option is a custom url category entry of FQDN/abc/* and block it with a url filtering profile. Can you block the Server by using FQDN defined object or is it a server that hosts multiple sites?

Hope this adds some value?

Phil

Re: http-req-uri-path limitation

vmusman — Thu, 18 Dec 2014 21:10:30 GMT

So to elaborate on Dave's questiom - some sites on this server need to be allowed while others need to be blocked. Also, blocking uri's with an app id only seems to work when attempted from firefox for some reason.