internetarchive / internetarchive/draintasker
upload fails with 400 because s3-launch-transfer sends bad Content-MD5 header
Open
- Dominant language
- Python
- Stars
- 11
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
this happens when:
- there are two WARCs A and B,
- filename A is a substring of filename B
s3-launch-transfer.sh uses naiive grep for retrieving MD5 hash for A from MANIFEST, resulting in extracting two MD5 hashes with newline in between, which goes straight into --header option for curl.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.