[GH-ISSUE #123] 403 on glob of directory named with comma #78

New issue

Closed

opened 2026-03-04 01:41:48 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 01:41:48 +03:00

Owner

Originally created by @ikolinahr on GitHub (Feb 14, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/123

**** UPDATE ****

This seems to be the same problem as noted in issue #118. The problem with both space and comma in directory names was introduced in version 1.78. Version 1.77 works fine.

Assume the following files in your s3 bucket:

dir/dir1/file1
dir/dir,2/file2
dir/dir3/file,3

The following commands will succeed:

ls dir
ls dir/dir1
ls dir/dir3
ls dir/dir1/file1
ls dir/dir,2/file2
ls dir/dir3/file,3

However, this will fail with a 403 error from AWS:

ls dir/dir,2

This is important for use when mounting encfs on top of s3fs-fuse. Encfs will name files with commas.

Originally created by @ikolinahr on GitHub (Feb 14, 2015). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/123 ***\* UPDATE **** This seems to be the same problem as noted in issue #118. The problem with both space and comma in directory names was introduced in version 1.78. Version 1.77 works fine. --- Assume the following files in your s3 bucket: dir/dir1/file1 dir/dir,2/file2 dir/dir3/file,3 The following commands will succeed: ls dir ls dir/dir1 ls dir/dir3 ls dir/dir1/file1 ls dir/dir,2/file2 ls dir/dir3/file,3 However, this will fail with a 403 error from AWS: ls dir/dir,2 This is important for use when mounting encfs on top of s3fs-fuse. Encfs will name files with commas.

kerem closed this issue

2026-03-04 01:41:49 +03:00

kerem commented

2026-03-04 01:41:49 +03:00

Author

Owner

@ggtakec commented on GitHub (Mar 21, 2015):

#154 is merged to master branch.
It probably fixed this issue(as same as #118), please test it.

I closed this issue, but if you have a problem yet, please reopen this issue.
Thanks for your help.

@ggtakec commented on GitHub (Mar 21, 2015): #154 is merged to master branch. It probably fixed this issue(as same as #118), please test it. I closed this issue, but if you have a problem yet, please reopen this issue. Thanks for your help.