Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content-Encoding in xattrs #97

Open
max-arnold opened this issue Dec 25, 2023 · 5 comments
Open

Content-Encoding in xattrs #97

max-arnold opened this issue Dec 25, 2023 · 5 comments

Comments

@max-arnold
Copy link

Is it possible to get content-encoding (and content-type) via xattrs?

Right now in Yandex Cloud Functions mounted bucket I only see s3.etag and user.mtime (as retrieved by Python's os.listxattr)

@max-arnold
Copy link
Author

The use case is to detect whether a file is compressed (gzip, brotli) and serve it via a Cloud Function using appropriate http headers

@vitalif
Copy link
Collaborator

vitalif commented Dec 27, 2023

Hi, it seems S3 ListObjects responses miss Content-Type for objects. ListObjects also missed UserMetadata. And GeeseFS tries to not perform HEAD requests for individual objects because it's really slow. Because of that, Yandex now has ListObjects list-type=ext-v1 which includes UserMetadata, but it seems it still misses ContentType :) so it should be implemented on the server first.

@max-arnold
Copy link
Author

Am I correct that currently there is no way to access the Content-Type attribute even with an extra HEAD request through GeeseFS?

If yes, do you recommend to keep this issue open, or it is better to file a feature request against YC?

@vitalif
Copy link
Collaborator

vitalif commented Dec 27, 2023

With an extra HEAD request it's possible but I don't really want to implement it this way

@max-arnold
Copy link
Author

Ok, submitted a feature request to YC. Let's keep this issue open for a while

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants