Currently, if uploading client does not provide a checksum and checksum type, FormKiQ uses an "upload" checksum from S3, which does not work as a content comparison checksum.
Ideally, we would provide the option to trigger a CHECKSUM action that takes a checksumType as a parameter (SHA-256, SHA-1) and sets the standard metadata items checksum and checksumType.
We will keep the etag "upload" checksum as default for the time being, but may remove in future updates.
Currently, if uploading client does not provide a checksum and checksum type, FormKiQ uses an "upload" checksum from S3, which does not work as a content comparison checksum.
Ideally, we would provide the option to trigger a CHECKSUM action that takes a checksumType as a parameter (SHA-256, SHA-1) and sets the standard metadata items
checksumandchecksumType.We will keep the etag "upload" checksum as default for the time being, but may remove in future updates.