New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Content-Type auto-detection #6097
Remove Content-Type auto-detection #6097
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Writing these docs made me realize we might have a naming/hierarchy problem anyway. I'll explain in chat.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-Authored-By: mpl <mathieu.lonjaret@gmail.com>
c57ee35
to
e1e9c06
Compare
What does this PR do?
This PR removes the auto-detection of the
Content-Type
.Motivation
When the backend doesn't send a
Content-Type
header, Traefik tried to auto-detect aContent-Type
. For a CSS, Traefik will detecttext/plain
and browser will not interperet css if it's intext/plain
and will interpret it if there is noContent-Type
.Fixes #6092 #4761 #3131
More
Co-Authored-By: mpl mathieu.lonjaret@gmail.com