<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Custom URL wildcard in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10960#M8086</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, so the wildcard in the URL-filter makes no distinction between URI-path and the host portion? Is that true in all releases?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 Nov 2011 09:56:52 GMT</pubDate>
    <dc:creator>rapoint_person</dc:creator>
    <dc:date>2011-11-18T09:56:52Z</dc:date>
    <item>
      <title>Custom URL wildcard</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10955#M8081</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a question relating to wildcards in a Custom URL Category on PA-500 - 4.1.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have the following entry in my custom URL category&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; *.centos.org&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and I'm finding that I'm getting a match with the following URL (and many others)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mirror.ox.ac.uk/sites/mirror.centos.org/5.7/updates/i386/RPMS/kernel-2.6.18-274.7.1.el5.i686.rpm&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this correct please? What I intended to match on was server-x.centos.org/, server-y.centos.org etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any info would be appreciated!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many Thanks,&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Nov 2011 13:44:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10955#M8081</guid>
      <dc:creator>DavePalo</dc:creator>
      <dc:date>2011-11-15T13:44:00Z</dc:date>
    </item>
    <item>
      <title>Re: Custom URL wildcard</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10956#M8082</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*.centos.org&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;will match everything that comes in as &amp;lt;xyz&amp;gt;.centos.com&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so you will see multiple matches - as you do.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If however, you'd like to be able to match ONLY and not any of the others&lt;/P&gt;&lt;P&gt;server-x.centos.org/, server-y.centos.org &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;then you may have to specify the URLs explicitly&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Nov 2011 19:42:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10956#M8082</guid>
      <dc:creator>sjamaluddin</dc:creator>
      <dc:date>2011-11-17T19:42:37Z</dc:date>
    </item>
    <item>
      <title>Re: Custom URL wildcard</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10957#M8083</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your reply!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My issue is that *.centos.org matches URLs that contain this string anywhere, rather than just the host name portion of the URL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Nov 2011 22:00:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10957#M8083</guid>
      <dc:creator>DavePalo</dc:creator>
      <dc:date>2011-11-17T22:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: Custom URL wildcard</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10958#M8084</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dave,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the example you provided:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="color:#000000;font-family:Arial, Helvetica, sans-serif;font-size:12px;background-color:#eef4f9"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; *.centos.org&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="color:#000000;font-family:Arial, Helvetica, sans-serif;font-size:12px;background-color:#eef4f9"&gt;and I'm finding that I'm getting a match with the following URL (and many others)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="color:#000000;font-family:Arial, Helvetica, sans-serif;font-size:12px;background-color:#eef4f9"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mirror.ox.ac.uk/sites/mirror.centos.org/5.7/updates/i386/RPMS/kernel-2.6.18-274.7.1.el5.i686.rpm&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this is expected behavior, since the wildcard matches anything before ".centos.org"&amp;nbsp; The example URL you provided matched because you have "mirror.ox.ac.uk/sites/mirror" preceding the pattern you defined.&amp;nbsp; Is your intention to only match when the URL only has one token preceding ".centos.org"?&amp;nbsp; For example, match "abc.centos.org" and not "def.abc.centos.org"?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--Doris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Nov 2011 22:30:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10958#M8084</guid>
      <dc:creator>dyang</dc:creator>
      <dc:date>2011-11-17T22:30:47Z</dc:date>
    </item>
    <item>
      <title>Re: Custom URL wildcard</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10959#M8085</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Doris,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks - it's my intention to match any host name ending in .centos.org&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example,&lt;/P&gt;&lt;P&gt;server.centos.org/blah/blah/&lt;/P&gt;&lt;P&gt;other.server.centos.org/blah/blah/blah/&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; but not&lt;/P&gt;&lt;P&gt;&lt;SPAN style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469);"&gt;mirror.ox.ac.uk/sites/mirror.centos.org/5.7/updates/i386/RPMS/kernel-2.6.18-274.7.1.el5.i686.rpm&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469);"&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469);"&gt;Dave&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Nov 2011 07:45:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10959#M8085</guid>
      <dc:creator>DavePalo</dc:creator>
      <dc:date>2011-11-18T07:45:54Z</dc:date>
    </item>
    <item>
      <title>Re: Custom URL wildcard</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10960#M8086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, so the wildcard in the URL-filter makes no distinction between URI-path and the host portion? Is that true in all releases?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Nov 2011 09:56:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10960#M8086</guid>
      <dc:creator>rapoint_person</dc:creator>
      <dc:date>2011-11-18T09:56:52Z</dc:date>
    </item>
    <item>
      <title>Re: Custom URL wildcard</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10961#M8087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does anybody know if this is the case please?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Nov 2011 12:21:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10961#M8087</guid>
      <dc:creator>DavePalo</dc:creator>
      <dc:date>2011-11-22T12:21:39Z</dc:date>
    </item>
    <item>
      <title>Re: Custom URL wildcard</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10962#M8088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dave,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Oskar (in the post before yours) is correct - currently the wildcard will look for the specified pattern in both the host as well as the path, and this behavior should be the same across all releases.&amp;nbsp; We hope to address the ability to limit patterns to either the host or the path in an upcoming release, so stay tuned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Doris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Nov 2011 02:09:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10962#M8088</guid>
      <dc:creator>dyang</dc:creator>
      <dc:date>2011-11-23T02:09:26Z</dc:date>
    </item>
    <item>
      <title>Re: Custom URL wildcard</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10963#M8089</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, thanks for the info. Hope this does change in a future release. I bet 99.9% of us using the feature in question are under the assumption that the pattern is matched against the host portion of the URL.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Nov 2011 09:53:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10963#M8089</guid>
      <dc:creator>rapoint_person</dc:creator>
      <dc:date>2011-11-23T09:53:17Z</dc:date>
    </item>
    <item>
      <title>Re: Custom URL wildcard</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10964#M8090</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you both for your help!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes this would be a most useful enhancement and would bring it in line with how I thought it worked!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Dave&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Nov 2011 10:04:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/custom-url-wildcard/m-p/10964#M8090</guid>
      <dc:creator>DavePalo</dc:creator>
      <dc:date>2011-11-23T10:04:11Z</dc:date>
    </item>
  </channel>
</rss>

