<?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: Unexpected behaviour URl filtering web in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224914#M64563</link>
    <description>&lt;P&gt;In this case it is at least related to TLS decryption. Without TLS decryption configured the firewall is not able to inject the continue page and because of that you probably have this traffic log entry when users go directly to the encrypted version of the website.&lt;/P&gt;&lt;P&gt;When the users manually enter http:// then as you wrote the users are able to see the continue page and continue also to the website right?&lt;/P&gt;</description>
    <pubDate>Mon, 06 Aug 2018 09:35:17 GMT</pubDate>
    <dc:creator>Remo</dc:creator>
    <dc:date>2018-08-06T09:35:17Z</dc:date>
    <item>
      <title>Unexpected behaviour URl filtering web</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224883#M64553</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are having a unexpected behaviour with PA identifying a web:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"rose.pharmaintelligence.informa.com"&lt;/P&gt;&lt;P&gt;This web is categorize like "news". We have in our URL profile "continue". But we are seeing that this web is being denied with reason "policy deny". Why PA is not allowing this web?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="URL.JPG" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/16148i850A48A9BDE5CC4F/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="URL.JPG" alt="URL.JPG" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="url news.JPG" style="width: 722px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/16149iC4AAF3271D97B7AE/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="url news.JPG" alt="url news.JPG" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="traffic.JPG" style="width: 795px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/16150i38945D259C968233/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="traffic.JPG" alt="traffic.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 07:46:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224883#M64553</guid>
      <dc:creator>BigPalo</dc:creator>
      <dc:date>2018-08-06T07:46:58Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected behaviour URl filtering web</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224892#M64554</link>
      <description>&lt;P&gt;It would be helpful to see the full traffic log, fields such as the session end reason etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do you have HTTPS inspection activated?&lt;/P&gt;&lt;P&gt;Do you see the continue page?&lt;/P&gt;&lt;P&gt;Does continue work for other HTTPS sites?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does the site use certificate pinning?&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 08:03:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224892#M64554</guid>
      <dc:creator>Philip_Wiberg</dc:creator>
      <dc:date>2018-08-06T08:03:00Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected behaviour URl filtering web</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224904#M64559</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/85066"&gt;@BigPalo&lt;/a&gt;&lt;/P&gt;&lt;P&gt;With almost 100% certainty, this is because of TLS decryption. What pan-os version are you using?&lt;/P&gt;&lt;P&gt;The issue here could be related to the fact that this site already supports TLS1.3 and the firewall somehow does not understand the TLS handshake correctly even if a connection with TLS1.2 is still possible.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Try to configure a decryption exception to check if it then works. &lt;STRIKE&gt;But anyway, in this case I would recommend to open a TAC case.&lt;/STRIKE&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 09:00:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224904#M64559</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2018-08-06T09:00:32Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected behaviour URl filtering web</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224910#M64560</link>
      <description>&lt;P&gt;When end-customer access to this web by https received a security event about security stuff. So customer delete https, and put http so the continue web is showed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;No decrypt ssl policy in the FW&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PanOs is 8.0.3&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 08:45:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224910#M64560</guid>
      <dc:creator>BigPalo</dc:creator>
      <dc:date>2018-08-06T08:45:07Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected behaviour URl filtering web</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224914#M64563</link>
      <description>&lt;P&gt;In this case it is at least related to TLS decryption. Without TLS decryption configured the firewall is not able to inject the continue page and because of that you probably have this traffic log entry when users go directly to the encrypted version of the website.&lt;/P&gt;&lt;P&gt;When the users manually enter http:// then as you wrote the users are able to see the continue page and continue also to the website right?&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 09:35:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224914#M64563</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2018-08-06T09:35:17Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected behaviour URl filtering web</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224916#M64565</link>
      <description>&lt;P&gt;Yes, but how can we change the TLS? any workaround?&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 09:43:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224916#M64565</guid>
      <dc:creator>BigPalo</dc:creator>
      <dc:date>2018-08-06T09:43:45Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected behaviour URl filtering web</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224917#M64566</link>
      <description>&lt;P&gt;Are the customers computers managed computers (where you could deploy a root CA cert)?&lt;/P&gt;&lt;P&gt;The best "workaround" probably is to configure TLS decryption to get a behaviour as it should be ...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PS: I would definately recommend to update to the latest recommended 8.0 release which is 8.0.10&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 09:50:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224917#M64566</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2018-08-06T09:50:16Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected behaviour URl filtering web</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224918#M64567</link>
      <description>&lt;P&gt;But customer is not doing decrypt ssl.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 09:51:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224918#M64567</guid>
      <dc:creator>BigPalo</dc:creator>
      <dc:date>2018-08-06T09:51:26Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected behaviour URl filtering web</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224919#M64568</link>
      <description>&lt;P&gt;Yes, I understood.&lt;/P&gt;&lt;P&gt;Then your only chance is this one here:&amp;nbsp;&lt;A href="https://live.paloaltonetworks.com/t5/Configuration-Articles/How-to-Serve-a-URL-Response-Page-Over-an-HTTPS-Session-Without/ta-p/55998" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Configuration-Articles/How-to-Serve-a-URL-Response-Page-Over-an-HTTPS-Session-Without/ta-p/55998&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 09:54:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224919#M64568</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2018-08-06T09:54:29Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected behaviour URl filtering web</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224920#M64569</link>
      <description>&lt;P&gt;OK, Perfect. So you have a response page "continue" and you access to https web, its mandatory to have decrypt ssl for this web? there no any way to identify this web without https decrypt?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;it was weird because the web it was identify in the correct category "news"&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 09:57:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224920#M64569</guid>
      <dc:creator>BigPalo</dc:creator>
      <dc:date>2018-08-06T09:57:54Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected behaviour URl filtering web</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224921#M64570</link>
      <description>&lt;P&gt;The URL I posted describes a way to serve the resonse page to users without TLS decryption.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The firewall is able to see the URL - at least the FQDN - in the TLS handshake even without decryption. But by default the firewall is not able to inject the response page into this connection as this is only possible when the firewall sees the actual http traffic. So try the solution in the url and hopefully this will solve the issue for you/your customer.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 10:02:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unexpected-behaviour-url-filtering-web/m-p/224921#M64570</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2018-08-06T10:02:15Z</dc:date>
    </item>
  </channel>
</rss>

