<?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: routing based on HTTP headers in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/routing-based-on-http-headers/m-p/330080#M821</link>
    <description>&lt;P&gt;We cannot route to the backend via an HTTP header.&amp;nbsp; We would typically deploy the ALB on the front side of the firewalls and use port address translation to maintain the application mapping through to the backend application.&amp;nbsp; Here is a sample diagram of what that would look like.&amp;nbsp; TGW is optional.&lt;/P&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="aws lb sandwich.png" style="width: 999px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/25860iD30E0DA6050165FE/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="aws lb sandwich.png" alt="aws lb sandwich.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 27 May 2020 14:14:35 GMT</pubDate>
    <dc:creator>jmeurer</dc:creator>
    <dc:date>2020-05-27T14:14:35Z</dc:date>
    <item>
      <title>routing based on HTTP headers</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/routing-based-on-http-headers/m-p/330034#M820</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi Team,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Does PA have the capability to perform routing based on HTTP headers, which can be leveraged to send the traffic to right ALB.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks in advance!!&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;&lt;P&gt;&lt;SPAN&gt;Om&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 27 May 2020 08:24:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/routing-based-on-http-headers/m-p/330034#M820</guid>
      <dc:creator>omprasadax</dc:creator>
      <dc:date>2020-05-27T08:24:01Z</dc:date>
    </item>
    <item>
      <title>Re: routing based on HTTP headers</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/routing-based-on-http-headers/m-p/330080#M821</link>
      <description>&lt;P&gt;We cannot route to the backend via an HTTP header.&amp;nbsp; We would typically deploy the ALB on the front side of the firewalls and use port address translation to maintain the application mapping through to the backend application.&amp;nbsp; Here is a sample diagram of what that would look like.&amp;nbsp; TGW is optional.&lt;/P&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="aws lb sandwich.png" style="width: 999px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/25860iD30E0DA6050165FE/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="aws lb sandwich.png" alt="aws lb sandwich.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 27 May 2020 14:14:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/routing-based-on-http-headers/m-p/330080#M821</guid>
      <dc:creator>jmeurer</dc:creator>
      <dc:date>2020-05-27T14:14:35Z</dc:date>
    </item>
  </channel>
</rss>

