<?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: SSL Forward Proxy for custom url with host and path in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/ssl-forward-proxy-for-custom-url-with-host-and-path/m-p/564977#M2028</link>
    <description>&lt;P&gt;how did you configure your decryption profile, and how is the custom server set up, does it have a full certificate path, is it a public or a selfsigned sever cert,..&lt;/P&gt;
&lt;P&gt;did you limit the ssl decryption rule using a custom url category for the custom url? if so how did you configure the category, did you add following urls:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;example.local/ 
example.local/*
*.example.local/ 
*.example.local/*&lt;/LI-CODE&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;
&lt;P&gt;ssl decryption will fully support any url and path as long as the protocol and certificates are working properly&lt;/P&gt;</description>
    <pubDate>Thu, 09 Nov 2023 12:59:41 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2023-11-09T12:59:41Z</dc:date>
    <item>
      <title>SSL Forward Proxy for custom url with host and path</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/ssl-forward-proxy-for-custom-url-with-host-and-path/m-p/564950#M2026</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SSL decrytion works if i set custom url with host only like &lt;A href="http://www.example.local," target="_blank"&gt;www.example.local,&lt;/A&gt;&amp;nbsp;but failed to decrypt if i set it as '&lt;A href="http://www.example.local/image/" target="_blank"&gt;www.example.local/image/&lt;/A&gt;'&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;i found article below, it should support custom url with host+path, but now i suspect will pan really support host+path decrption&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PMRlCAO" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PMRlCAO&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Nov 2023 08:58:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/ssl-forward-proxy-for-custom-url-with-host-and-path/m-p/564950#M2026</guid>
      <dc:creator>allenlwli</dc:creator>
      <dc:date>2023-11-09T08:58:32Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Forward Proxy for custom url with host and path</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/ssl-forward-proxy-for-custom-url-with-host-and-path/m-p/564977#M2028</link>
      <description>&lt;P&gt;how did you configure your decryption profile, and how is the custom server set up, does it have a full certificate path, is it a public or a selfsigned sever cert,..&lt;/P&gt;
&lt;P&gt;did you limit the ssl decryption rule using a custom url category for the custom url? if so how did you configure the category, did you add following urls:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;example.local/ 
example.local/*
*.example.local/ 
*.example.local/*&lt;/LI-CODE&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;
&lt;P&gt;ssl decryption will fully support any url and path as long as the protocol and certificates are working properly&lt;/P&gt;</description>
      <pubDate>Thu, 09 Nov 2023 12:59:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/ssl-forward-proxy-for-custom-url-with-host-and-path/m-p/564977#M2028</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2023-11-09T12:59:41Z</dc:date>
    </item>
  </channel>
</rss>

