topic URL wildcard use in Advanced Threat Prevention Discussions

URL wildcard use

raji_toor — Fri, 14 Sep 2018 17:37:38 GMT

We have insufficent-content category blocked. And when trying to allow a specific url using wildcard i am having issues.

when *.figuringoutmelody.com is used it is allowed on port 80 only while ssl gets blocked. website seems to redirect form www.figuringoutmelody.com to https://figuringoutmelody.com

and when i used figuringoutmelody.com just as is, it gets allowed on ssl without www but not on 80.

Isn't *.figuringoutmelody.com supposed to cover both www.*.figuringoutmelody.com and figuringoutmelody.com

Re: URL wildcard use

OtakarKlier — Tue, 18 Sep 2018 14:21:59 GMT

Hello,

No this is not the case. Check out this article:

https://www.paloaltonetworks.com/documentation/80/pan-os/pan-os/url-filtering/url-filtering-concepts/block-and-allow-lists

Basically *.xyz.com will match anything before the .xyz.com, i.e. www.xyz.com, ftp.xyz.com, mail.xyz.com, etc.

xyz.com will match if there is nothing before the xyz.com so www.xyz.com will NOT match this.

PAN recommends the following if you want to whitlist www.xyz.com. Enter both of the following:

xyz.com

*.xyz.com

Hope that helps.

Re: URL wildcard use

raji_toor — Wed, 19 Sep 2018 18:28:07 GMT

Thanks @OtakarKlier