Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove the HTTP header X-UA-Compatible #2224

Closed
bschmalhofer opened this issue Mar 9, 2023 · 2 comments
Closed

Remove the HTTP header X-UA-Compatible #2224

bschmalhofer opened this issue Mar 9, 2023 · 2 comments
Milestone
OTOBO 11.0

Comments

@bschmalhofer
Copy link
Contributor

The header X-UA-Compatible is set to IE=edge,chrome=1 in C< _AddHeadersToResponseObject> . I think that this header can be removed, as very old Microsoft Browser are no longer supported.

Originally posted by @bschmalhofer in #1617 (comment)
@bschmalhofer bschmalhofer added this to the OTOBO 11.0 milestone Mar 9, 2023
@bschmalhofer
Copy link
Contributor Author

OTOBOs only supported version of Internet Explorer is IE11. The current setting of X-UA-Compatible is to use the highest possible version. Thus it looks like this header can be removed. Let's do so.

See also: https://doc.otobo.org/manual/installation/10.1/en/content/requirements.html#software-requirements and https://www.mediaevent.de/meta/.

bschmalhofer added a commit that referenced this issue Mar 12, 2023
@bschmalhofer
Issue #2224: remove the HTTP header X-UA-Compatible
03d5e41 
Not needed for IE 11 and Microsoft Edge
bschmalhofer added a commit that referenced this issue Mar 12, 2023
@bschmalhofer
Merge pull request #2228 from RotherOSS/issue-#2224-x_ua_compatible
748769d 
Issue #2224: remove the HTTP header X-UA-Compatible
@bschmalhofer
Copy link
Contributor Author

The header has been removed. Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
OTOBO 11.0
Development

No branches or pull requests
1 participant
@bschmalhofer