Repository navigation
Getting Rid of http-equiv "X-UA-Compatible" tags #24841
Description
Activity
Thank you for reporting 👍
omit the X-UA-Compatible tags
I added a note to: #20855 (comment)
Deploying a server already requires full access to server configuration
That's not correct.
- linked a pull request that will close this issueRemove legacy Internet Explorer headers #31629
on Mar 19, 2022
Is your feature request related to a problem? Please describe.
When I search the codebase I see the http-equiv tag is only used for IE compatibility, which is phasing out. Going through the meta requires to interpret the beginning of the HTML page, which is slower than going through the HTTP headers in terms of performance
Describe the solution you'd like
Deploying a server already requires full access to server configuration so if there is still a need to provide this functionality we can do this in nginx or apache as defining the meta is the same as sending the HTTP Content-Type header.
Describe alternatives you've considered
Either omit the X-UA-Compatible tags or move it to the webserver