baalajimaestro/traefik
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Doc middleware compress content type

Browse source
This commit is contained in:
Romain 2020-04-29 11:26:04 +02:00 • committed by GitHub
parent 7c7ca7ef2b
commit e5c6b0d4ea
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
docs/content/middlewares/compress.md
View file

@ -64,6 +64,9 @@ http:
* The `Accept-Encoding` request header contains `gzip`. * The `Accept-Encoding` request header contains `gzip`.
* The response is not already compressed, i.e. the `Content-Encoding` response header is not already set. * The response is not already compressed, i.e. the `Content-Encoding` response header is not already set.
If Content-Type header is not defined, or empty, the compress middleware will automatically [detect](https://mimesniff.spec.whatwg.org/) a content type.
It will also set accordingly the `Content-Type` header with the detected MIME type.
## Configuration Options ## Configuration Options
### `excludedContentTypes` ### `excludedContentTypes`

3
docs/content/middlewares/contenttype.md
View file

@ -22,6 +22,9 @@ This middleware exists to enable the correct behavior until at least the default
Therefore, given the default value of the `autoDetect` option (false), Therefore, given the default value of the `autoDetect` option (false),
simply enabling this middleware for a router switches the router's behavior. simply enabling this middleware for a router switches the router's behavior.
The scope of the Content-Type middleware is the MIME type detection done by the core of Traefik (the server part).
Therefore, it has no effect against any other `Content-Type` header modifications (e.g.: in another middleware such as compress).
## Configuration Examples ## Configuration Examples
```yaml tab="Docker" ```yaml tab="Docker"