-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Invalid Warc Files #22
Comments
The
warcio.js probably should just default to warctools is very old and does not support WARC 1.1, your first warcinfo record is WARC 1.1, while the rest are 1.0 - changing that to 1.0 will actually have it pass... I realize additional examples will make it easier to use, will try to add them when I have chance! |
…and other records) if no warc content-type is specified addresses issue discussed in #22
Thanks so much for looking into this! On my initial tests, opening the file with the Unarchiver still failed, but I’ll be able to try more combinations late tonight or tomorrow. Are there any other items or sample files I could check? Yes, I was working on building flexible methods for saving resources related to the page that aren’t requests or responses. For compatibility, I can also try saving as a response type and see if that works. More examples are always welcome—most of what I learned so far was from the test cases and readme. |
I made the changes to calculate the warcHeaders { "Content-Type": "mime/type" } on each of my resources. I also tried removing my resources, but both The Unarchiver and jwattools still choked. How would you rate jwattools @ikreymer ? Not really sure what else to check or what’s different with the working Demo file: https://share.fromtheexchange.space/file/space-fromtheexchange-share/booya-no-resources.warc |
Originated from #21 (comment)
Files (links expire in 7 days):
Validators:
App:
The text was updated successfully, but these errors were encountered: