<?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: Http traffic to https in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/http-traffic-to-https/m-p/421257#M93931</link>
    <description>&lt;P&gt;Quick answer: bad idea.&lt;BR /&gt;&lt;BR /&gt;Long answer 1: it would probably confuse the browser, unlike an "HTTPS-only like" browser extension, which would do the same thing (in a non-centralized fashion, of course) while keeping the browser aware of the redirection&lt;BR /&gt;&lt;BR /&gt;Long answer 2: a PAN firewall seems to be able to "express" that kind of DNAT rule, should you want to try&lt;BR /&gt;&lt;BR /&gt;Possible solution:&lt;BR /&gt;- hijack the DNS domain and point it to an IP of yours (PAN dns-proxy should be able to do that with a static entry, in case you're using it)&lt;BR /&gt;- set up a "dummy" http-only web server with an HTTP/301 catch-all page that points to the https server (bonus point: implement a rewrite that keeps the URL)&lt;BR /&gt;- DNAT on firewall so that &lt;STRONG&gt;https&lt;/STRONG&gt; to YOUR dummy web server is DNAT'ed to the original one&lt;/P&gt;</description>
    <pubDate>Thu, 22 Jul 2021 09:22:12 GMT</pubDate>
    <dc:creator>michelealbrigo</dc:creator>
    <dc:date>2021-07-22T09:22:12Z</dc:date>
    <item>
      <title>Http traffic to https</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/http-traffic-to-https/m-p/421211#M93929</link>
      <description>&lt;P&gt;Hi Guys&amp;nbsp;&lt;BR /&gt;Can we redirect someone trying to access &lt;A href="http://www.xxx.com" target="_blank"&gt;http://www.xxx.com&lt;/A&gt; to &lt;A href="https://www.xxx.com" target="_blank"&gt;https://www.xxx.com&lt;/A&gt; ( port 80 to 443 ) ?&lt;/P&gt;&lt;P&gt;If we are using Dest NAT for &lt;A href="https://www.xxx.com" target="_blank"&gt;https://www.xxx.com&lt;/A&gt;&amp;nbsp;?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jul 2021 07:03:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/http-traffic-to-https/m-p/421211#M93929</guid>
      <dc:creator>i_maddy</dc:creator>
      <dc:date>2021-07-22T07:03:52Z</dc:date>
    </item>
    <item>
      <title>Re: Http traffic to https</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/http-traffic-to-https/m-p/421257#M93931</link>
      <description>&lt;P&gt;Quick answer: bad idea.&lt;BR /&gt;&lt;BR /&gt;Long answer 1: it would probably confuse the browser, unlike an "HTTPS-only like" browser extension, which would do the same thing (in a non-centralized fashion, of course) while keeping the browser aware of the redirection&lt;BR /&gt;&lt;BR /&gt;Long answer 2: a PAN firewall seems to be able to "express" that kind of DNAT rule, should you want to try&lt;BR /&gt;&lt;BR /&gt;Possible solution:&lt;BR /&gt;- hijack the DNS domain and point it to an IP of yours (PAN dns-proxy should be able to do that with a static entry, in case you're using it)&lt;BR /&gt;- set up a "dummy" http-only web server with an HTTP/301 catch-all page that points to the https server (bonus point: implement a rewrite that keeps the URL)&lt;BR /&gt;- DNAT on firewall so that &lt;STRONG&gt;https&lt;/STRONG&gt; to YOUR dummy web server is DNAT'ed to the original one&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jul 2021 09:22:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/http-traffic-to-https/m-p/421257#M93931</guid>
      <dc:creator>michelealbrigo</dc:creator>
      <dc:date>2021-07-22T09:22:12Z</dc:date>
    </item>
  </channel>
</rss>

