jrandall opened a new issue, #3642: URL: https://github.com/apache/incubator-opendal/issues/3642
I am building a service using opendal that refers certain GET requests to S3 using a presigned URL generated with the `Operator::presign_read_with` method and setting the range, override_content_disposition, override_cache_control, and override_content_type on the resulting `FuturePresignRead` object. This works great. However, I would now like my service to implement HEAD for these requests. I have done that using the `Operator::presign_stat` method, and this does work. However, I have test cases that validate the behavior for HEAD as specified in RFC7231 section 4.3.2 (https://datatracker.ietf.org/doc/html/rfc7231#section-4.3.2): ``` The server SHOULD send the same header fields in response to a HEAD request as it would have sent if the request had been a GET, except that the payload header fields ([Section 3.3](https://datatracker.ietf.org/doc/html/rfc7231#section-3.3)) MAY be omitted ``` Since I am asking S3 to override response headers and support a Range header in the request, I need to be able to pass these to the stat (HEAD) request as well in order to pass this test. It appears that S3 supports this, it is just that opendal does not expose these interfaces for stat. It would be useful if `Operator::presign_stat_with` and `opendal::operator_futures::FuturePresignStat` could both be implemented (though I believe it would be sensible for the latter to have exactly the same interface as `opendal::operator_futures::FuturePresignRead`, since a major use case for this would be to achieve parity between the results returned from a GET (S3 read) and HEAD (S3 stat) request). -- 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]
