mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #847] Problems listing buckets of S3 compatible service with virtual-host style requests #495
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#495
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ffeldhaus on GitHub (Oct 29, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/847
Additional Information
When connecting to an S3 compatible service, listing the bucket content fails.
Version of s3fs being used (s3fs --version)
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
Kernel information (uname -r)
GNU/Linux Distribution, if applicable (cat /etc/os-release)
s3fs command line used, if applicable
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
Details about issue
A thing which seems to be wrong is, that s3fs removes the / after the url (before
?delimiter) when using the default virtual-host style:As the same command works when specifying
-o use_path_request_styleI suspect that there is something wrong with virtual-host style, probably with rewriting the URL. DNS resolution of the bucket name (e.g. cloudmirror-1.s3.labdus.netapp.com) works without problems. Interestingly virtual-host style Bucket Listing works with AWS S3.@gaul commented on GitHub (Jul 11, 2019):
Do virtual-host style buckets work with other tools when using your non-AWS S3 service?
@ffeldhaus commented on GitHub (Jul 11, 2019):
The issue does not occur on newer releases of s3fs anymore, therefore closing the issue.