-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
WARC-Protocol + WARC-Cipher-Suite headers #715
base: main
Are you sure you want to change the base?
Conversation
…parated - add WARC-Cipher-Suite header, mapping Chrome NetworkSecurityDetails to known cipher suites - fixes #641
Re: the WARC-Protocol header being comma separated rather than repeated, it looks like the IIPC membership is trying to get consensus on whether this is acceptable this week. See ongoing discussion here: iipc/warc-specifications#42 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One suggestion re: import cleanup.
Community consensus in iipc/warc-specifications#42 seems to be for repeated headers rather than a single header with a comma-separated list so we should probably modify this PR to go with that approach.
support WARC-Protocol as multiple headers tests: add tests for WARC-Protocol, WARC-Cipher-Suite
Co-authored-by: Tessa Walsh <[email protected]>
Updated to now generate multiple WARC-Protocol headers, per consensus there. |
Though, may also want to get clarification on WARC-Cipher-Suite since its not an exact one-to-one mapping there.. |
A few caveats: