Use the same case everywhere

docs/content/https/tls.md

@@ -13,7 +13,7 @@ See the [Let's Encrypt](./acme.md) page.
 
 To add / remove TLS certificates, even when Traefik is already running, their definition can be added to the [dynamic configuration](../getting-started/configuration-overview.md), in the `[[tls.certificates]]` section:
 
-```toml
+```toml tab="TOML"
 [[tls.certificates]]
   certFile = "/path/to/domain.cert"
   keyFile = "/path/to/domain.key"
@@ -23,6 +23,15 @@ To add / remove TLS certificates, even when Traefik is already running, their de
   keyFile = "/path/to/other-domain.key"
 ```
 
+```yaml tab="YAML"
+tls:
+  certificates:
+  - certFile: /path/to/domain.cert
+    keyFile: /path/to/domain.key
+  - certFile: /path/to/other-domain.cert
+    keyFile: /path/to/other-domain.key
+```
+
 !!! important "File Provider Only"
 
     In the above example, we've used the [file provider](../providers/file.md) to handle these definitions.
@@ -32,23 +41,29 @@ To add / remove TLS certificates, even when Traefik is already running, their de
 
 In Traefik, certificates are grouped together in certificates stores, which are defined as such:
 
-```toml
+```toml tab="TOML"
 [tls.stores]
   [tls.stores.default]
 ```
 
+```yaml tab="YAML"
+tls:
+  stores:
+    default: {}
+```
+
 !!! important "Alpha restriction"
 
     During the alpha version, any store definition other than the default one (named `default`) will be ignored,
     and there is thefore only one globally available TLS store.
 
-In the `[[tls.certificates]]` section, a list of stores can then be specified to indicate where the certificates should be stored:
+In the `tls.certificates` section, a list of stores can then be specified to indicate where the certificates should be stored:
 
-```toml
+```toml tab="TOML"
 [[tls.certificates]]
-  stores = ["default"]
   certFile = "/path/to/domain.cert"
   keyFile = "/path/to/domain.key"
+  stores = ["default"]
 
 [[tls.certificates]]
   # Note that since no store is defined,
@@ -57,6 +72,19 @@ In the `[[tls.certificates]]` section, a list of stores can then be specified to
   keyFile = "/path/to/other-domain.key"
 ```
 
+```yaml tab="YAML"
+tls:
+  certificates:
+  - certFile: /path/to/domain.cert
+    keyFile: /path/to/domain.key
+    stores:
+    - default
+  # Note that since no store is defined,
+  # the certificate below will be stored in the `default` store.
+  - certFile: /path/to/other-domain.cert
+    keyFile: /path/to/other-domain.key
+```
+
 !!! important "Alpha restriction"
 
     During the alpha version, the `stores` list will actually be ignored and automatically set to `["default"]`.
@@ -66,7 +94,7 @@ In the `[[tls.certificates]]` section, a list of stores can then be specified to
 Traefik can use a default certificate for connections without a SNI, or without a matching domain.
 This default certificate should be defined in a TLS store:
 
-```toml
+```toml tab="TOML"
 [tls.stores]
   [tls.stores.default]
     [tls.stores.default.defaultCertificate]
@@ -74,6 +102,15 @@ This default certificate should be defined in a TLS store:
       keyFile  = "path/to/cert.key"
 ```
 
+```yaml tab="YAML"
+tls:
+  stores:
+    default:
+      defaultCertificate:
+        certFile: path/to/cert.crt
+        keyFile: path/to/cert.key
+```
+
 If no default certificate is provided, Traefik generates and uses a self-signed certificate.
 
 ## TLS Options
@@ -82,7 +119,7 @@ The TLS options allow one to configure some parameters of the TLS connection.
 
 ### Minimum TLS Version
 
-```toml
+```toml tab="TOML"
 [tls.options]
 
   [tls.options.default]
@@ -92,6 +129,16 @@ The TLS options allow one to configure some parameters of the TLS connection.
     minVersion = "VersionTLS13"
 ```
 
+```yaml tab="YAML"
+tls:
+  options:
+    default:
+      minVersion: VersionTLS12
+
+    mintls13:
+      minVersion: VersionTLS13
+```
+
 ### Mutual Authentication
 
 Traefik supports both optional and strict (which is the default) mutual authentication, though the `ClientCA.files` section.
@@ -102,20 +149,32 @@ For clients with a certificate, the `optional` option governs the behaviour as f
 - When `optional = false`, Traefik accepts connections only from clients presenting a certificate signed by a CA listed in `ClientCA.files`.
 - When `optional = true`, Traefik authorizes connections from clients presenting a certificate signed by an unknown CA.
 
-```toml
+```toml tab="TOML"
 [tls.options]
   [tls.options.default]
-    [tls.options.default.ClientCA]
+    [tls.options.default.clientCA]
       # in PEM format. each file can contain multiple CAs.
       files = ["tests/clientca1.crt", "tests/clientca2.crt"]
       optional = false
 ```
 
+```yaml tab="YAML"
+tls:
+  options:
+    default:
+      clientCA:
+        # in PEM format. each file can contain multiple CAs.
+        files:
+        - tests/clientca1.crt
+        - tests/clientca2.crt
+        optional: false
+```
+
 ### Cipher Suites
 
 See [cipherSuites](https://godoc.org/crypto/tls#pkg-constants) for more information.
 
-```toml
+```toml tab="TOML"
 [tls.options]
   [tls.options.default]
     cipherSuites = [
@@ -124,13 +183,29 @@ See [cipherSuites](https://godoc.org/crypto/tls#pkg-constants) for more informat
     ]
 ```
 
+```yaml tab="YAML"
+tls:
+  options:
+    default:
+      cipherSuites:
+      - TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
+      - TLS_RSA_WITH_AES_256_GCM_SHA384
+```
+
 ### Strict SNI Checking
 
 With strict SNI checking, Traefik won't allow connections from clients connections
 that do not specify a server_name extension.
 
-```toml
+```toml tab="TOML"
 [tls.options]
   [tls.options.default]
     sniStrict = true
 ```
+
+```yaml tab="YAML"
+tls:
+  options:
+    default:
+      sniStrict: true
+```