<?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: https inspection tip/feedback/suggestion in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/https-inspection-tip-feedback-suggestion/m-p/253152#M42467</link>
    <description>&lt;P&gt;I find this a bit too restrictive, if you set it up from the beginning and before fine-tuning the policy. For lab purposes, and for demos, no issue.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Jul 2025 07:13:59 GMT</pubDate>
    <dc:creator>_Val_</dc:creator>
    <dc:date>2025-07-15T07:13:59Z</dc:date>
    <item>
      <title>https inspection tip/feedback/suggestion</title>
      <link>https://community.checkpoint.com/t5/General-Topics/https-inspection-tip-feedback-suggestion/m-p/253038#M42425</link>
      <description>&lt;P&gt;Hey guys,&lt;/P&gt;
&lt;P&gt;Happy weekend &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Since few customers asked me about this, figured would share what works BEST in my lab from R81.20 and R82 testing. I also had clients do the same and they had not had any issues since. I find having fail mode set to block, as well as categorization to background 100% helps to avoid any inspection/block page issues.&lt;/P&gt;
&lt;P&gt;I attached screenshots of what Im referring to.&lt;/P&gt;
&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Sat, 12 Jul 2025 15:29:00 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/https-inspection-tip-feedback-suggestion/m-p/253038#M42425</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-07-12T15:29:00Z</dc:date>
    </item>
    <item>
      <title>Re: https inspection tip/feedback/suggestion</title>
      <link>https://community.checkpoint.com/t5/General-Topics/https-inspection-tip-feedback-suggestion/m-p/253152#M42467</link>
      <description>&lt;P&gt;I find this a bit too restrictive, if you set it up from the beginning and before fine-tuning the policy. For lab purposes, and for demos, no issue.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 07:13:59 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/https-inspection-tip-feedback-suggestion/m-p/253152#M42467</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2025-07-15T07:13:59Z</dc:date>
    </item>
    <item>
      <title>Re: https inspection tip/feedback/suggestion</title>
      <link>https://community.checkpoint.com/t5/General-Topics/https-inspection-tip-feedback-suggestion/m-p/253183#M42481</link>
      <description>&lt;P&gt;I found it works best even in production, but guess it depends on the exact scenario.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 12:21:34 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/https-inspection-tip-feedback-suggestion/m-p/253183#M42481</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-07-15T12:21:34Z</dc:date>
    </item>
  </channel>
</rss>

