<?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: Internal URL Filtering in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/internal-url-filtering/m-p/1537566#M588740</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;The ASA can act as an URL-filtering proxy when using Websense or N2H2 (it has a different name now)....&lt;/P&gt;&lt;P&gt;The ASA will intercept the HTTP traffic and send it to the server... but this happens if the traffic goes through the firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In other words, if the traffic will not go through the firewall, there's no way the firewall will intercept it correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Perhaps you can elaborate your question so we can help you out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Federico.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 29 Nov 2010 22:32:50 GMT</pubDate>
    <dc:creator>Federico Coto Fajardo</dc:creator>
    <dc:date>2010-11-29T22:32:50Z</dc:date>
    <item>
      <title>Internal URL Filtering</title>
      <link>https://community.cisco.com/t5/network-security/internal-url-filtering/m-p/1537565#M588739</link>
      <description>&lt;P&gt;I am using McAfee/Secure Computing URL filter service.&amp;nbsp; I want to require authentication when the user opens the browser which points to an internal site (inside interface), and therefore doesn't require that the user pass through the firewall to get there.&amp;nbsp; How can I force the authentication for users when the home page is internal - without having them go to an outside url?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 19:16:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/internal-url-filtering/m-p/1537565#M588739</guid>
      <dc:creator>william.culver</dc:creator>
      <dc:date>2019-03-11T19:16:03Z</dc:date>
    </item>
    <item>
      <title>Re: Internal URL Filtering</title>
      <link>https://community.cisco.com/t5/network-security/internal-url-filtering/m-p/1537566#M588740</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;The ASA can act as an URL-filtering proxy when using Websense or N2H2 (it has a different name now)....&lt;/P&gt;&lt;P&gt;The ASA will intercept the HTTP traffic and send it to the server... but this happens if the traffic goes through the firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In other words, if the traffic will not go through the firewall, there's no way the firewall will intercept it correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Perhaps you can elaborate your question so we can help you out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Federico.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Nov 2010 22:32:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/internal-url-filtering/m-p/1537566#M588740</guid>
      <dc:creator>Federico Coto Fajardo</dc:creator>
      <dc:date>2010-11-29T22:32:50Z</dc:date>
    </item>
  </channel>
</rss>

