

Buffering

How to Read the Request before Forwarding It

The Buffering middleware gives you control on how you want to read the requests before sending them to services.

With Buffering, Traefik reads the entire request into memory (possibly buffering large requests into disk), and rejects requests that are over a specified limit.

This can help services deal with large data (multipart/form-data for example), and can minimize time spent sending data to a service.

Configuration Examples

Docker

# Sets the maximum request body to 2Mb
labels:
  - "traefik.http.middlewares.limit.buffering.maxRequestBodyBytes=2000000"

Kubernetes

# Sets the maximum request body to 2Mb
apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: limit
spec:
  buffering:
    maxRequestBodyBytes: 2000000

Marathon

"labels": {
  "traefik.http.middlewares.limit.buffering.maxRequestBodyBytes": "2000000"
}

Rancher

# Sets the maximum request body to 2Mb
labels:
  - "traefik.http.middlewares.limit.buffering.maxRequestBodyBytes=2000000"

File (TOML)

# Sets the maximum request body to 2Mb
[http.middlewares]
  [http.middlewares.limit.buffering]
    maxRequestBodyBytes = 2000000

File (YAML)

# Sets the maximum request body to 2Mb
http:
  middlewares:
    limit:
      buffering:
        maxRequestBodyBytes: 2000000

Configuration Options

maxRequestBodyBytes

With the maxRequestBodyBytes option, you can configure the maximum allowed body size for the request (in Bytes).

If the request exceeds the allowed size, it is not forwarded to the service and the client gets a 413 (Request Entity Too Large) response.

Docker

labels:
  - "traefik.http.middlewares.limit.buffering.maxRequestBodyBytes=2000000"

Kubernetes

apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: limit
spec:
  buffering:
    maxRequestBodyBytes: 2000000

Marathon

"labels": {
  "traefik.http.middlewares.limit.buffering.maxRequestBodyBytes": "2000000"
}

Rancher

labels:
  - "traefik.http.middlewares.limit.buffering.maxRequestBodyBytes=2000000"

File (TOML)

[http.middlewares]
  [http.middlewares.limit.buffering]
    maxRequestBodyBytes = 2000000

File (YAML)

http:
  middlewares:
    limit:
      buffering:
        maxRequestBodyBytes: 2000000

memRequestBodyBytes

You can configure a threshold (in Bytes) from which the request will be buffered on disk instead of in memory with the memRequestBodyBytes option.

Docker

labels:
  - "traefik.http.middlewares.limit.buffering.memRequestBodyBytes=2000000"

Kubernetes

apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: limit
spec:
  buffering:
    memRequestBodyBytes: 2000000

Marathon

"labels": {
  "traefik.http.middlewares.limit.buffering.memRequestBodyBytes": "2000000"
}

Rancher

labels:
  - "traefik.http.middlewares.limit.buffering.memRequestBodyBytes=2000000"

File (TOML)

[http.middlewares]
  [http.middlewares.limit.buffering]
    memRequestBodyBytes = 2000000

File (YAML)

http:
  middlewares:
    limit:
      buffering:
        memRequestBodyBytes: 2000000

maxResponseBodyBytes

With the maxReesponseBodyBytes option, you can configure the maximum allowed response size from the service (in Bytes).

If the response exceeds the allowed size, it is not forwarded to the client. The client gets a 413 (Request Entity Too Large) response instead.

Docker

labels:
  - "traefik.http.middlewares.limit.buffering.maxResponseBodyBytes=2000000"

Kubernetes

apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: limit
spec:
  buffering:
    maxResponseBodyBytes: 2000000

Marathon

"labels": {
  "traefik.http.middlewares.limit.buffering.maxResponseBodyBytes": "2000000"
}

Rancher

labels:
  - "traefik.http.middlewares.limit.buffering.maxResponseBodyBytes=2000000"

File (TOML)

[http.middlewares]
  [http.middlewares.limit.buffering]
    maxResponseBodyBytes = 2000000

File (YAML)

http:
  middlewares:
    limit:
      buffering:
        maxResponseBodyBytes: 2000000

memResponseBodyBytes

You can configure a threshold (in Bytes) from which the response will be buffered on disk instead of in memory with the memResponseBodyBytes option.

Docker

labels:
  - "traefik.http.middlewares.limit.buffering.memResponseBodyBytes=2000000"

Kubernetes

apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: limit
spec:
  buffering:
    memResponseBodyBytes: 2000000

Marathon

"labels": {
  "traefik.http.middlewares.limit.buffering.memResponseBodyBytes": "2000000"
}

Rancher

labels:
  - "traefik.http.middlewares.limit.buffering.memResponseBodyBytes=2000000"

File (TOML)

[http.middlewares]
  [http.middlewares.limit.buffering]
    memResponseBodyBytes = 2000000

File (YAML)

http:
  middlewares:
    limit:
      buffering:
        memResponseBodyBytes: 2000000

retryExpression

You can have the Buffering middleware replay the request with the help of the retryExpression option.

Retries once in case of a network error

Docker

labels:
  - "traefik.http.middlewares.limit.buffering.retryExpression=IsNetworkError() && Attempts() < 2"

Kubernetes

apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: limit
spec:
  buffering:
    retryExpression: "IsNetworkError() && Attempts() < 2"

Marathon

"labels": {
  "traefik.http.middlewares.limit.buffering.retryExpression": "IsNetworkError() && Attempts() < 2"
}

Rancher

labels:
  - "traefik.http.middlewares.limit.buffering.retryExpression=IsNetworkError() && Attempts() < 2"

File (TOML)

[http.middlewares]
  [http.middlewares.limit.buffering]
    retryExpression = "IsNetworkError() && Attempts() < 2"

File (YAML)

http:
  middlewares:
    limit:
      buffering:
        retryExpression: "IsNetworkError() && Attempts() < 2"

The retry expression is defined as a logical combination of the functions below with the operators AND (&&) and OR (||). At least one function is required:

• Attempts() number of attempts (the first one counts)
• ResponseCode() response code of the service
• IsNetworkError() - if the response code is related to networking error