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

hash checking should be lenient #251

Open
tokee opened this issue Jun 7, 2021 · 0 comments
Open

hash checking should be lenient #251

tokee opened this issue Jun 7, 2021 · 0 comments

Comments

@tokee
Copy link
Collaborator

tokee commented Jun 7, 2021

The warc-indexer currently calculate a single hash for content when indexing. As #234, #222 and #233 shows, hash calculation for WARC entries is a mess. For validation purposes warc-indexer should calculate all hashes in all the different ways that are encountered in the wild and don't warn if one of them matches.

@anjackson anjackson added this to the 3.1.1 Bugfix Release milestone Aug 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants