Deploy GitHub Pages

user-guide/miscellaneous/index.html

@@ -676,6 +676,13 @@
     Source IP address
   </a>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#path-types" class="md-nav__link">
+    Path types
+  </a>
+  
 </li>
       
         <li class="md-nav__item">
@@ -1176,6 +1183,13 @@
     Source IP address
   </a>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#path-types" class="md-nav__link">
+    Path types
+  </a>
+  
 </li>
       
         <li class="md-nav__item">
@@ -1246,6 +1260,9 @@
 <p>If the ingress controller is running in AWS we need to use the VPC IPv4 CIDR.</p>
 <p>Another option is to enable proxy protocol using <code>use-proxy-protocol: "true"</code>.</p>
 <p>In this mode NGINX does not use the content of the header to get the source IP address of the connection.</p>
+<h2 id="path-types">Path types<a class="headerlink" href="#path-types" title="Permanent link"> ¶</a></h2>
+<p>Each path in an Ingress is required to have a corresponding path type. Paths that do not include an explicit pathType will fail validation.
+By default NGINX path type is Prefix to not break existing definitions</p>
 <h2 id="proxy-protocol">Proxy Protocol<a class="headerlink" href="#proxy-protocol" title="Permanent link"> ¶</a></h2>
 <p>If you are using a L4 proxy to forward the traffic to the NGINX pods and terminate HTTP/HTTPS there, you will lose the remote endpoint's IP address. To prevent this you could use the <a href="http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt">Proxy Protocol</a> for forwarding traffic, this will send the connection details before forwarding the actual TCP connection itself.</p>
 <p>Amongst others <a href="http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/enable-proxy-protocol.html">ELBs in AWS</a> and <a href="http://www.haproxy.org/">HAProxy</a> support Proxy Protocol.</p>