homelab/traefik
1
0
Fork 0
Code Activity

Merge v2.6 into master

Browse source
This commit is contained in:
romain 2022-03-24 17:22:56 +01:00
commit 8d58f33a28
4 changed files with 33 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/content/https/acme.md
View file

@ -25,7 +25,7 @@ You can read more about this retrieval mechanism in the following section: [ACME
!!! warning "Defining an [ACME challenge type](#the-different-acme-challenges) is a requirement for a certificate resolver to be functional."
!!! important "Defining a certificates resolver does not result in all routers automatically using it. Each router that is supposed to use the resolver must [reference](../routing/routers/index.md#certresolver) it."
!!! important "Defining a certificate resolver does not result in all routers automatically using it. Each router that is supposed to use the resolver must [reference](../routing/routers/index.md#certresolver) it."
??? note "Configuration Reference"
@ -116,7 +116,7 @@ Please check the [configuration examples below](#configuration-examples) for mor
--certificatesresolvers.myresolver.acme.httpchallenge.entrypoint=web
```
!!! important "Defining a certificates resolver does not result in all routers automatically using it. Each router that is supposed to use the resolver must [reference](../routing/routers/index.md#certresolver) it."
!!! important "Defining a certificate resolver does not result in all routers automatically using it. Each router that is supposed to use the resolver must [reference](../routing/routers/index.md#certresolver) it."
??? example "Single Domain from Router's Rule Example"
@ -145,7 +145,7 @@ Traefik automatically tracks the expiry date of ACME certificates it generates.
By default, Traefik manages 90 days certificates,
and starts to renew certificates 30 days before their expiry.
When using a certificates resolver that issues certificates with custom durations,
When using a certificate resolver that issues certificates with custom durations,
one can configure the certificates' duration with the [`certificatesDuration`](#certificatesduration) option.
!!! info ""
@ -162,7 +162,7 @@ When using LetsEncrypt with kubernetes, there are some known caveats with both t
!!! warning "Defining one ACME challenge is a requirement for a certificate resolver to be functional."
!!! important "Defining a certificates resolver does not result in all routers automatically using it. Each router that is supposed to use the resolver must [reference](../routing/routers/index.md#certresolver) it."
!!! important "Defining a certificate resolver does not result in all routers automatically using it. Each router that is supposed to use the resolver must [reference](../routing/routers/index.md#certresolver) it."
### `tlsChallenge`

6
docs/content/routing/entrypoints.md
View file

@ -258,7 +258,8 @@ In most scenarios, this entryPoint is the same as the one used for TLS traffic.
```
```bash tab="CLI"
--experimental.http3=true --entrypoints.name.http3
--experimental.http3=true
--entrypoints.name.http3
```
#### `advertisedPort`
@ -288,7 +289,8 @@ It can be used to override the authority in the `alt-svc` header, for example if
```
```bash tab="CLI"
--experimental.http3=true --entrypoints.name.http3.advertisedport=443
--experimental.http3=true
--entrypoints.name.http3.advertisedport=443
```
### Forwarded Headers