[GH-ISSUE #1662] Look at GCS-specific headers #870

Closed
opened 2026-03-04 01:49:31 +03:00 by kerem · 4 comments
Owner

Originally created by @gaul on GitHub (May 20, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1662

s3fs should have a GCS mode which uses headers like x-goog-storage-class instead of x-amz-storage-class:

https://cloud.google.com/storage/docs/xml-api/reference-headers#xgoogstorageclass

Related to #1613.

Originally created by @gaul on GitHub (May 20, 2021). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1662 s3fs should have a GCS mode which uses headers like `x-goog-storage-class` instead of `x-amz-storage-class`: https://cloud.google.com/storage/docs/xml-api/reference-headers#xgoogstorageclass Related to #1613.
kerem closed this issue 2026-03-04 01:49:32 +03:00
Author
Owner

@ggtakec commented on GitHub (May 20, 2021):

@gaul Should we switch to use x-goog-meta-* and x-amz-meta* properly?

<!-- gh-comment-id:845058903 --> @ggtakec commented on GitHub (May 20, 2021): @gaul Should we switch to use `x-goog-meta-*` and `x-amz-meta*` properly?
Author
Owner

@gaul commented on GitHub (May 20, 2021):

I think we might want to add a --gcs flag or automatically change to GCS mode based on --url matching storage.googleapis.com.

<!-- gh-comment-id:845075969 --> @gaul commented on GitHub (May 20, 2021): I think we might want to add a `--gcs` flag or automatically change to GCS mode based on `--url` matching storage.googleapis.com.
Author
Owner

@ggtakec commented on GitHub (May 20, 2021):

Both look good. However, considering that there may be such differences in other parts in the future, I think the --gcs option seems to be better.

<!-- gh-comment-id:845148341 --> @ggtakec commented on GitHub (May 20, 2021): Both look good. However, considering that there may be such differences in other parts in the future, I think the `--gcs` option seems to be better.
Author
Owner

@gaul commented on GitHub (May 22, 2021):

This bug may be invalid. GCS supports x-amz-storage-class and it doesn't appear that the other headers provide any value, except for conditional PUT. I think there are some other ETag sanity checks that we should do before looking at vendor-specific conditional PUT though.

<!-- gh-comment-id:846359365 --> @gaul commented on GitHub (May 22, 2021): This bug may be invalid. GCS supports `x-amz-storage-class` and it doesn't appear that the other headers provide any value, except for conditional PUT. I think there are some other ETag sanity checks that we should do before looking at vendor-specific conditional PUT though.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#870
No description provided.