sk106623: "Custom Application/Site that was created to match a domain and sub-domains, is not matched by Application & URL Filtering policy"

Document created by jean-b380a05f-304b-42a4-b4a2-eb81d813c9ea on Feb 18, 2018
Version 1Show Document
  • View in full screen mode

Introductory note: Since some documents haven't been given the little love they deserve IMHO, I'm going to document my findings and proposals for improving them here, for everyone's benefit. Usually, I've tried giving feedback in said articles, but either they didn't change anything (even though they said I was correct) or they just didn't understand what I meant.

 

So, about sk106623:

 

This article is so wrong in many places.

The actual solution to the symptom is very simple and does not need regexes at all. You specify an application and put two items in it:

  • *.example.com
  • example.com

Done.

 

Furthermore, the regexes they are proposing are not safe: \.example\.com would also match "x.example.com.bla" or even worse "http://site.com/bla/blubb.example.com.bla/index.htm" except if there were implicit anchors that one should be aware of.

 

Finally, there is a note that says \.example\.com would match both "example.com" and subdomains "*.example.com" which simply is not true. \.example\.com will not match "example.com".

2 people found this helpful

Attachments

    Outcomes