RedirectScheme

The RedirectScheme middleware redirects the request if the request scheme is different from the configured scheme.

When behind another reverse-proxy

When there is at least one other reverse-proxy between the client and Traefik, the other reverse-proxy (for example, the last hop) needs to be a [trusted] one.

Otherwise, Traefik would clean up the X-Forwarded headers coming from this last hop, and as the RedirectScheme middleware relies on them to determine the scheme used, it would not function as intended.

---

Configuration Options

permanent

Field	Description
permanent	Set the permanent option to true to apply a permanent redirection.

301 Redirect

apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
  name: test-redirectscheme
spec:
  redirectScheme:
    permanent: true

scheme

Field	Description
scheme	The scheme option defines the scheme of the new URL.

Redirect to HTTPS

apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
  name: test-redirectscheme
spec:
  redirectScheme:
    scheme: https

port

Field	Description
port	The port option defines the port of the new URL.

note

Port in this configuration is a string, not a numeric value.

Using ports

apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
  name: test-redirectscheme
spec:
  redirectScheme:
    port: "443"

Example

301 to https

apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
  name: test-redirectscheme
spec:
  redirectScheme:
    scheme: https
    permanent: true