DevFW-CICD/ingress-nginx-helm
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Deploy GitHub Pages

Browse source
This commit is contained in:
Travis Bot 2019-04-20 18:13:57 +00:00
parent 0f3d14b10b
commit d0b5bbbb19
6 changed files with 76 additions and 50 deletions
Download patch file Download diff file Expand all files Collapse all files

5
user-guide/nginx-configuration/annotations/index.html
View file

@ -2036,6 +2036,10 @@ table below.</p>
<td>string</td>
</tr>
<tr>
<td><a href="#custom-timeouts">nginx.ingress.kubernetes.io/proxy-next-upstream-timeout</a></td>
<td>number</td>
</tr>
<tr>
<td><a href="#custom-timeouts">nginx.ingress.kubernetes.io/proxy-next-upstream-tries</a></td>
<td>number</td>
</tr>
@ -2545,6 +2549,7 @@ In some scenarios is required to have different values. To allow this we provide
<li><code class="codehilite">nginx.ingress.kubernetes.io/proxy-send-timeout</code></li>
<li><code class="codehilite">nginx.ingress.kubernetes.io/proxy-read-timeout</code></li>
<li><code class="codehilite">nginx.ingress.kubernetes.io/proxy-next-upstream</code></li>
<li><code class="codehilite">nginx.ingress.kubernetes.io/proxy-next-upstream-timeout</code></li>
<li><code class="codehilite">nginx.ingress.kubernetes.io/proxy-next-upstream-tries</code></li>
<li><code class="codehilite">nginx.ingress.kubernetes.io/proxy-request-buffering</code></li>
</ul>

21
user-guide/nginx-configuration/configmap/index.html
View file

@ -1362,6 +1362,13 @@
proxy-next-upstream
</a>
</li>
<li class="md-nav__item">
<a href="#proxy-next-upstream-timeout" title="proxy-next-upstream-timeout" class="md-nav__link">
proxy-next-upstream-timeout
</a>
</li>
<li class="md-nav__item">
@ -2796,6 +2803,13 @@
proxy-next-upstream
</a>
</li>
<li class="md-nav__item">
<a href="#proxy-next-upstream-timeout" title="proxy-next-upstream-timeout" class="md-nav__link">
proxy-next-upstream-timeout
</a>
</li>
<li class="md-nav__item">
@ -3521,6 +3535,11 @@ Same for numbers, like "100".</p>
<td align="left">"error timeout"</td>
</tr>
<tr>
<td align="left"><a href="#proxy-next-upstream-timeout">proxy-next-upstream-timeout</a></td>
<td align="left">int</td>
<td align="left">0</td>
</tr>
<tr>
<td align="left"><a href="#proxy-next-upstream-tries">proxy-next-upstream-tries</a></td>
<td align="left">int</td>
<td align="left">3</td>
@ -3974,6 +3993,8 @@ See NGINX <a href="http://nginx.org/en/docs/http/ngx_http_core_module.html#clien
<p>Sets a text that <a href="http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cookie_domain">should be changed in the domain attribute</a> of the “Set-Cookie” header fields of a proxied server response.</p>
<h2 id="proxy-next-upstream">proxy-next-upstream<a class="headerlink" href="#proxy-next-upstream" title="Permanent link">&para;</a></h2>
<p>Specifies in <a href="http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_next_upstream">which cases</a> a request should be passed to the next server.</p>
<h2 id="proxy-next-upstream-timeout">proxy-next-upstream-timeout<a class="headerlink" href="#proxy-next-upstream-timeout" title="Permanent link">&para;</a></h2>
<p><a href="http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_next_upstream_timeout">Limits the time</a> in seconds during which a request can be passed to the next server.</p>
<h2 id="proxy-next-upstream-tries">proxy-next-upstream-tries<a class="headerlink" href="#proxy-next-upstream-tries" title="Permanent link">&para;</a></h2>
<p>Limit the number of <a href="http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_next_upstream_tries">possible tries</a> a request should be passed to the next server.</p>
<h2 id="proxy-redirect-from">proxy-redirect-from<a class="headerlink" href="#proxy-redirect-from" title="Permanent link">&para;</a></h2>