<?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: Bypass the url filtering in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/bypass-the-url-filtering/m-p/518030#M490</link>
    <description>&lt;P&gt;Thank you for reply. Could you share some more detail information ?&lt;/P&gt;</description>
    <pubDate>Mon, 17 Oct 2022 02:34:11 GMT</pubDate>
    <dc:creator>kiennn</dc:creator>
    <dc:date>2022-10-17T02:34:11Z</dc:date>
    <item>
      <title>Bypass the url filtering</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/bypass-the-url-filtering/m-p/517981#M488</link>
      <description>&lt;P&gt;Hi everyone&lt;/P&gt;
&lt;P&gt;Can bypass the url filtering by&amp;nbsp;changing the URL in HTTP get request ?&lt;BR /&gt;For example&lt;BR /&gt;Firewall rule deny connect to url deny.com and allow url allow.com&lt;BR /&gt;User try to connect to deny.com with IP adress a.b.c.d, user add item the host file or using plugin/extension of browsers to change http request to allow.com but destination ip address in packet is a.b.c.d&lt;BR /&gt;Firewall will allow the request, so user can connect to deny.com by IP address ?&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 14 Oct 2022 17:38:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/bypass-the-url-filtering/m-p/517981#M488</guid>
      <dc:creator>kiennn</dc:creator>
      <dc:date>2022-10-14T17:38:04Z</dc:date>
    </item>
    <item>
      <title>Re: Bypass the url filtering</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/bypass-the-url-filtering/m-p/518009#M489</link>
      <description>&lt;P&gt;For HTTPS the firewall can categorise it based on the certificate CN received, which is not something the client can falsify.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For plaintext HTTP traffic, the only information available is the HTTP host header, so it will be categorised based on that.&lt;/P&gt;</description>
      <pubDate>Sat, 15 Oct 2022 22:03:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/bypass-the-url-filtering/m-p/518009#M489</guid>
      <dc:creator>dmifsud</dc:creator>
      <dc:date>2022-10-15T22:03:43Z</dc:date>
    </item>
    <item>
      <title>Re: Bypass the url filtering</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/bypass-the-url-filtering/m-p/518030#M490</link>
      <description>&lt;P&gt;Thank you for reply. Could you share some more detail information ?&lt;/P&gt;</description>
      <pubDate>Mon, 17 Oct 2022 02:34:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/bypass-the-url-filtering/m-p/518030#M490</guid>
      <dc:creator>kiennn</dc:creator>
      <dc:date>2022-10-17T02:34:11Z</dc:date>
    </item>
  </channel>
</rss>

