dentiny commented on PR #7884: URL: https://github.com/apache/opendal/pull/7884#issuecomment-4926332061
> However, I did find their error listing which has one [MissingContentLength](https://docs.netapp.com/us-en/storagegrid/s3/error-responses.html#supported-s3-api-error-codes:~:text=MissingContentLength) that makes me think they care about this. I'm not sure this is the best way to handle. :thinking_face: - Assuming it's netapp ONTAP-9, I don't see content-length required for any operation: https://docs.netapp.com/us-en/ontap/pdfs/fullsite-sidebar/ONTAP_9_documentation.pdf - For the missing content-length, I'm not sure whether the server side is expecting 0 or a real object size + A missing-length error is not convincing to me - It's not open source, it's not well-documented (at least I didn't find it), I don't find docker image, I'm wondering how can we verify we're doing the correct thing? I'm actually thinking if we could allow users to inject their customized headers - I hope opendal-core to implement only S3 spec, but not un-documented behavior from all types of vendors + For example, what if another S3-compatible vendor expecting content-length to be object size? - It's legal and natural for different S3-compatible impls could accept their own headers + I'm working on an internal object storage for my current job, we discussed a bit on exposing some headers to better control server-side caching policy for performance, and passing checksum for validation, etc -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
