Middlewares

    Attached to the routers, pieces of middleware are a means of tweaking the requests before they are sent to your service (or before the answer from the services are sent to the clients).

    There are several available middleware in Traefik, some can modify the request, the headers, some are in charge of redirections, some add authentication, and so on.

    Middlewares that use the same protocol can be combined into chains to fit every scenario.

    Provider Namespace

    Docker

    Kubernetes IngressRoute

    2. apiVersion: traefik.containo.us/v1alpha1
    3. kind: Middleware
    4. metadata:
    5.   name: stripprefix
    6. spec:
    7.   stripPrefix:
    8.     prefixes:
    9.       - /stripit
    11. ---
    12. apiVersion: traefik.containo.us/v1alpha1
    13. kind: IngressRoute
    15. spec:
    16. # more fields...
    17.   routes:
    18.     # more fields...
    19.     middlewares:
    20.       - name: stripprefix

    Consul Catalog

    Marathon

    1. "labels": {
    2.   "traefik.http.middlewares.foo-add-prefix.addprefix.prefix": "/foo",
    3.   "traefik.http.routers.router1.middlewares": "[email protected]"
    4. }

    Rancher

    1. # As YAML Configuration File
    2. http:
    3.   routers:
    5.       middlewares:
    6.         - "foo-add-prefix"
    7.       rule: "Host(`example.com`)"
    9.   middlewares:
    10.     foo-add-prefix:
    11.       addPrefix:
    12.         prefix: "/foo"
    14.   services:
    15.     service1:
    16.       loadBalancer:
    18.           - url: "http://127.0.0.1:80"

    File (TOML)

    Available Middlewares

    A list of HTTP middlewares can be found .

    A list of TCP middlewares can be found here.

    Using Traefik for Business Applications?

    If you are using Traefik for commercial applications, consider the . You can use it as your: