dentiny commented on PR #7884: URL: https://github.com/apache/opendal/pull/7884#issuecomment-4929281824
Thanks! I create a feature request [here](https://github.com/apache/opendal/issues/7894) to track. > we can go ahead with this PR at least. Sure, but I do have a few practical questions: - Do we have any concrete conclusion that the netapp S3 is expecting a header of "Content-Length: 0", or it's expecting users to provide actual object size? Since it's undocumented and untested, I have no clue whether this PR will address the original issue - It's completely unknown whether there's a vendor who take advantage of the Content-Length header for indicate the number of bytes to copy (I won't be surprised if any vendors implements so); that way we're introducing new failures -- that's the conflict behavior I mentioned on the issue - If go with the custom header solution -- at least you seem to agree on it :wink: -- how do we plan to deal with the content-length header in this PR? If we plan to delete it, it's a behavior change... At minimum we should leave a TODO IMO -- 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]
