<?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: Manual URL Filtering in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/manual-url-filtering/m-p/4688547#M1093443</link>
    <description>&lt;P&gt;Thanks for the response. Yes they are in the right order. What you posted is what I have been using as a reference. To further update, the next day when I came back in to the office the block wasn't working either and the allow rule was disabled. I am going to have to create a ticket with TAC as the filter is definitely not working as stated.&lt;/P&gt;</description>
    <pubDate>Fri, 16 Sep 2022 12:07:33 GMT</pubDate>
    <dc:creator>gcook0001</dc:creator>
    <dc:date>2022-09-16T12:07:33Z</dc:date>
    <item>
      <title>Manual URL Filtering</title>
      <link>https://community.cisco.com/t5/network-security/manual-url-filtering/m-p/4687410#M1093374</link>
      <description>&lt;P&gt;I am working trying to limit users to certain sites within a domain using manual url filtering.&lt;/P&gt;&lt;P&gt;I have a rule that blocks discord.com which works&lt;/P&gt;&lt;P&gt;I do want users to be able to access certain channels within discord.&lt;/P&gt;&lt;P&gt;source: internal network&lt;/P&gt;&lt;P&gt;destination: discord.com/login&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; (I tried this with https:// as well)&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; discord.com/channels/@me&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (I tried this with https:// as well)&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;discord.com/channels/1019669992859516958/1019669992859516961&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (I tried this with https:// as well)&lt;/P&gt;&lt;P&gt;Action: allow&lt;/P&gt;&lt;P&gt;source: internal network&lt;/P&gt;&lt;P&gt;destination: discord.com&lt;/P&gt;&lt;P&gt;action: block&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't get access to the three links above. According to the documentation on manual url filtering if a / is detected then it matchs the whole string.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2022 20:41:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/manual-url-filtering/m-p/4687410#M1093374</guid>
      <dc:creator>gcook0001</dc:creator>
      <dc:date>2022-09-14T20:41:32Z</dc:date>
    </item>
    <item>
      <title>Re: Manual URL Filtering</title>
      <link>https://community.cisco.com/t5/network-security/manual-url-filtering/m-p/4687866#M1093406</link>
      <description>&lt;P&gt;Gcook, are you placing your URLs you want to allow before your discord.com block in your ACL? Here is what I found on the "/" character. Is this the documentation you are referencing?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="000789.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/162627i5BFDBF92FA73E65B/image-size/large?v=v2&amp;amp;px=999" role="button" title="000789.png" alt="000789.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Sep 2022 13:12:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/manual-url-filtering/m-p/4687866#M1093406</guid>
      <dc:creator>Alan Inman</dc:creator>
      <dc:date>2022-09-15T13:12:42Z</dc:date>
    </item>
    <item>
      <title>Re: Manual URL Filtering</title>
      <link>https://community.cisco.com/t5/network-security/manual-url-filtering/m-p/4688547#M1093443</link>
      <description>&lt;P&gt;Thanks for the response. Yes they are in the right order. What you posted is what I have been using as a reference. To further update, the next day when I came back in to the office the block wasn't working either and the allow rule was disabled. I am going to have to create a ticket with TAC as the filter is definitely not working as stated.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 12:07:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/manual-url-filtering/m-p/4688547#M1093443</guid>
      <dc:creator>gcook0001</dc:creator>
      <dc:date>2022-09-16T12:07:33Z</dc:date>
    </item>
  </channel>
</rss>

