<?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: worldarchitecturenews.com is blocked in URL filtering by news category in Panorama Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/panorama-discussions/worldarchitecturenews-com-is-blocked-in-url-filtering-by-news/m-p/455572#M608</link>
    <description>&lt;P&gt;There was a problem with this post, so I modified the link to show the entire message now.&lt;/P&gt;</description>
    <pubDate>Mon, 27 Dec 2021 18:07:33 GMT</pubDate>
    <dc:creator>jdelio</dc:creator>
    <dc:date>2021-12-27T18:07:33Z</dc:date>
    <item>
      <title>worldarchitecturenews.com is blocked in URL filtering by news category</title>
      <link>https://live.paloaltonetworks.com/t5/panorama-discussions/worldarchitecturenews-com-is-blocked-in-url-filtering-by-news/m-p/454005#M583</link>
      <description>&lt;P data-unlink="true"&gt;The URL:&amp;nbsp;&lt;A href="http://worldarchitecturenews.com/" target="_blank" rel="noopener" data-saferedirecturl="https://www.google.com/url?q=http://worldarchitecturenews.com&amp;amp;source=gmail&amp;amp;ust=1639849205575000&amp;amp;usg=AOvVaw2Nf-e7IVep5mAI5mJmRDS4"&gt;worldarchitecturenews&lt;WBR /&gt;.com&lt;/A&gt; &amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P data-unlink="true"&gt;was earlier accessible through port 80 but later on it migrated to port : 443 and it became inaccessible. Giving block page when trying to access the URL. The URL is blocked under news category with no Application ID found and action is block-URL.&lt;/P&gt;
&lt;P data-unlink="true"&gt;Please suggest how to unblock this URL. So that it becomes accessible under news category for all users on port 443.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Dec 2021 18:06:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/panorama-discussions/worldarchitecturenews-com-is-blocked-in-url-filtering-by-news/m-p/454005#M583</guid>
      <dc:creator>Dhatwar</dc:creator>
      <dc:date>2021-12-27T18:06:58Z</dc:date>
    </item>
    <item>
      <title>Re: worldarchitecturenews.com is blocked in URL filtering by news category</title>
      <link>https://live.paloaltonetworks.com/t5/panorama-discussions/worldarchitecturenews-com-is-blocked-in-url-filtering-by-news/m-p/455572#M608</link>
      <description>&lt;P&gt;There was a problem with this post, so I modified the link to show the entire message now.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Dec 2021 18:07:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/panorama-discussions/worldarchitecturenews-com-is-blocked-in-url-filtering-by-news/m-p/455572#M608</guid>
      <dc:creator>jdelio</dc:creator>
      <dc:date>2021-12-27T18:07:33Z</dc:date>
    </item>
    <item>
      <title>Re: worldarchitecturenews.com is blocked in URL filtering by news category</title>
      <link>https://live.paloaltonetworks.com/t5/panorama-discussions/worldarchitecturenews-com-is-blocked-in-url-filtering-by-news/m-p/455585#M609</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;You mentioned "&lt;SPAN&gt;&amp;nbsp;with no Application ID&amp;nbsp;", this could be why. I would suggest you look at the policy it should hit and make sure it has both applications, web-browsing and ssl. Also if you are ssl decrypting the traffic, and running&amp;nbsp;an older code version, pre 9, you might have to specify the service, e.g. ports, also.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Dec 2021 19:09:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/panorama-discussions/worldarchitecturenews-com-is-blocked-in-url-filtering-by-news/m-p/455585#M609</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2021-12-27T19:09:00Z</dc:date>
    </item>
  </channel>
</rss>

