http-req-uri-path limitation

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

http-req-uri-path limitation

L0 Member

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:

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


L5 Sessionator


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

Hope it helps !

L4 Transporter


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?


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.

  • 3 replies
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!