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

Content-Security-Policy handling #16

Open
grantat opened this issue Oct 4, 2017 · 0 comments
Open

Content-Security-Policy handling #16

grantat opened this issue Oct 4, 2017 · 0 comments

Comments

@grantat
Copy link
Member

grantat commented Oct 4, 2017

Web.archive.org introduced a new Content-Security-Policy for live web leaking into the mementos and memento-damage isn't really handling them. Here is one example:

A lot of the images don't return a proper response code and are rendered in the page as empty. This should be affecting damage even though they don't have a proper response code.

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

1 participant