Custom URL to match allow policy matches halfway through URL

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Custom URL to match allow policy matches halfway through URL

L1 Bithead

Custom URL category containing one line similar to this:

After the domain name are a series of strings with some dashes and forward slashes. String5 is meant to be a filename in the string3-string4 directory.

The URL category matches in an allow rule for web-browsing port 80 traffic. No decryption here. No special NAT. 

These seem to match the rule:<anything> 

so basically as long as the firewall reads the end of string2 it matches regardless of anything after string2.

For now it works for our purposes, but we only want to catch a specific file, so, any idea why it would do this? 

Thanks in advance for reading. I promise I tried my best to read documentation and previous posts!


Cyber Elite
Cyber Elite

So you want it to match for "<anything>"?


Use filter:*


And maybe* as is needed as well.

Enterprise Architect, Security @ Cloud Carib Ltd
Palo Alto Networks certified from 2011


These seem to match the rule:<anything> 

But we want exactly this:


L1 Bithead

To put it another way, what should I input so this exact text is matched and nothing else: ?

From my reading of the documentation that is exactly what I am supposed to input. I think I do not have to put in regex or an extra slash at the end. 

  • 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!