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.

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

Double x-frame-options header on Listed.to #221

Open
salixh5 opened this issue Nov 16, 2021 · 0 comments
Open

Double x-frame-options header on Listed.to #221

salixh5 opened this issue Nov 16, 2021 · 0 comments

Comments

@salixh5
Copy link

salixh5 commented Nov 16, 2021

Describe the bug
Any website on the listed.to domain and all listed.to custom domains return multiple x-frame-options headers. They're also both different (sameorigin and deny). Browsers don't expect multiple x-frame-options headers and this results in undefined behavior. You should only send a single x-frame-options header.

To Reproduce
Steps to reproduce the behavior:

  1. Go to listed.to
  2. Look at the HTTP headers

More
X-Content-Type-Options is also doubled up, but contains the same content both times. Could still confuse some browsers and should be avoided. Also you probably don't want to send X-Powered-By and Server headers in production.

@ghost ghost assigned karolsojko Dec 28, 2021
@moughxyz moughxyz transferred this issue from standardnotes/forum Dec 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants