<?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: Cisco ASA 5510 and Smartfilter issues with https sites in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-asa-5510-and-smartfilter-issues-with-https-sites/m-p/1156605#M876018</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In the ACNS 5.2.3 software and later releases, you can configure a Content Engine to bypass URL filtering for certain HTTP and HTTPS requests. This feature is supported for local list URL filtering (good and bad site lists), as well as Websense, SmartFilter, or N2H2 URL filtering. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, if you enable local URL filtering on the Content Engine and enable the bad sites deny feature (for example, the badfile.txt file contains the URLs that should be blocked), and the rule no-url-filtering action is a hit (a match), the Content Engine bypasses the URL filtering for that particular request; otherwise, it proceeds with URL filtering and blocks the URL request. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 26 Feb 2009 22:52:41 GMT</pubDate>
    <dc:creator>pradeepde</dc:creator>
    <dc:date>2009-02-26T22:52:41Z</dc:date>
    <item>
      <title>Cisco ASA 5510 and Smartfilter issues with https sites</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-5510-and-smartfilter-issues-with-https-sites/m-p/1156604#M876017</link>
      <description>&lt;P&gt;We have smartfilter 4.2.1 setup for transparent authentication and set up with Cisco 5510. The http filtering works great. We are having a lot of issues with https sites. The users randomly keep getting page cannot be displayed errors with https sites. When they click refresh the page comes back. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anybody experienced this or knows of a solution? Smartfilter support hasn't been able to find one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vrushali&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 14:54:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-5510-and-smartfilter-issues-with-https-sites/m-p/1156604#M876017</guid>
      <dc:creator>ja1064</dc:creator>
      <dc:date>2019-03-11T14:54:12Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA 5510 and Smartfilter issues with https sites</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-5510-and-smartfilter-issues-with-https-sites/m-p/1156605#M876018</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In the ACNS 5.2.3 software and later releases, you can configure a Content Engine to bypass URL filtering for certain HTTP and HTTPS requests. This feature is supported for local list URL filtering (good and bad site lists), as well as Websense, SmartFilter, or N2H2 URL filtering. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, if you enable local URL filtering on the Content Engine and enable the bad sites deny feature (for example, the badfile.txt file contains the URLs that should be blocked), and the rule no-url-filtering action is a hit (a match), the Content Engine bypasses the URL filtering for that particular request; otherwise, it proceeds with URL filtering and blocks the URL request. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Feb 2009 22:52:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-5510-and-smartfilter-issues-with-https-sites/m-p/1156605#M876018</guid>
      <dc:creator>pradeepde</dc:creator>
      <dc:date>2009-02-26T22:52:41Z</dc:date>
    </item>
  </channel>
</rss>

