<?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: Checkpoint as a Proxy-Block Page in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Checkpoint-as-a-Proxy-Block-Page/m-p/145661#M22977</link>
    <description>&lt;P&gt;HTTPS Inspection must be enabled for HTTPS UserCheck pages to work as a redirect is required, which requires injecting a redirect into the connection.&lt;BR /&gt;That can’t be done without decrypting and reencrypting the traffic.&lt;/P&gt;</description>
    <pubDate>Thu, 07 Apr 2022 03:30:16 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2022-04-07T03:30:16Z</dc:date>
    <item>
      <title>Checkpoint as a Proxy-Block Page</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Checkpoint-as-a-Proxy-Block-Page/m-p/145652#M22971</link>
      <description>&lt;P&gt;I am well aware of the fact that when a user visits a "blocked" http url , CP will redirect the user to a UserCheck block page.&lt;/P&gt;&lt;P&gt;Can the aforementioned behavior be accomplished with HTTPs urls as well and without https inspection enabled ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, provided that I configure Checkpoint as a non-transparent proxy and that I only have "HTTPs Categorize Sites" enabled, if my users visit a https web page that gets blocked by the URL filtering blade, will CP return to the user a UserCheck Block Page ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2022 20:55:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Checkpoint-as-a-Proxy-Block-Page/m-p/145652#M22971</guid>
      <dc:creator>Nikolaos_Liakop</dc:creator>
      <dc:date>2022-04-06T20:55:23Z</dc:date>
    </item>
    <item>
      <title>Re: Checkpoint as a Proxy-Block Page</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Checkpoint-as-a-Proxy-Block-Page/m-p/145653#M22972</link>
      <description>&lt;P&gt;I dont think there is any way to have that behavior without inspection enabled, because in that case, yes, page wont work, but block notification will never come up, as there is nothing to be intercepted by the firewall, since the inspection cert that would have been presented when https inspection is on, would not be there.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2022 23:43:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Checkpoint-as-a-Proxy-Block-Page/m-p/145653#M22972</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2022-04-06T23:43:38Z</dc:date>
    </item>
    <item>
      <title>Re: Checkpoint as a Proxy-Block Page</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Checkpoint-as-a-Proxy-Block-Page/m-p/145661#M22977</link>
      <description>&lt;P&gt;HTTPS Inspection must be enabled for HTTPS UserCheck pages to work as a redirect is required, which requires injecting a redirect into the connection.&lt;BR /&gt;That can’t be done without decrypting and reencrypting the traffic.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Apr 2022 03:30:16 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Checkpoint-as-a-Proxy-Block-Page/m-p/145661#M22977</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2022-04-07T03:30:16Z</dc:date>
    </item>
  </channel>
</rss>

