<?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 pix url filtering in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-url-filtering/m-p/1603777#M592928</link>
    <description>&lt;DIV class="jive-rendered-content"&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this is very new to me. can we do filter based on url.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) deny external users access to following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ab.def.com:80&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) allow external users to have access to following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ab.def.com:80/ex/servlet&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can we do this? I'm kinda new this kind of filtering...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pls advise.&lt;/P&gt;&lt;/DIV&gt;</description>
    <pubDate>Mon, 11 Mar 2019 19:43:20 GMT</pubDate>
    <dc:creator>gavin han</dc:creator>
    <dc:date>2019-03-11T19:43:20Z</dc:date>
    <item>
      <title>pix url filtering</title>
      <link>https://community.cisco.com/t5/network-security/pix-url-filtering/m-p/1603777#M592928</link>
      <description>&lt;DIV class="jive-rendered-content"&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this is very new to me. can we do filter based on url.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) deny external users access to following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ab.def.com:80&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) allow external users to have access to following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ab.def.com:80/ex/servlet&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can we do this? I'm kinda new this kind of filtering...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pls advise.&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 11 Mar 2019 19:43:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-url-filtering/m-p/1603777#M592928</guid>
      <dc:creator>gavin han</dc:creator>
      <dc:date>2019-03-11T19:43:20Z</dc:date>
    </item>
    <item>
      <title>Re: pix url filtering</title>
      <link>https://community.cisco.com/t5/network-security/pix-url-filtering/m-p/1603778#M592930</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As far as i know you cant't let only the Pix handle this.&lt;/P&gt;&lt;P&gt;Maybe with the "url-server (inside) 192.168.x.x " ? (i don't have any experience with this feature).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think you can better block this at the webserver itself with a .htaccess file or something simular.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Feb 2011 13:24:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-url-filtering/m-p/1603778#M592930</guid>
      <dc:creator>Niels van der Made</dc:creator>
      <dc:date>2011-02-02T13:24:56Z</dc:date>
    </item>
  </channel>
</rss>

