In swift3 middleware, Access to lower case container was denied
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Swift3 |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
I will report two bug about swift3 middleware.
I created container TEST1 and test1
# date
Wed May 14 16:05:56 JST 2014
# swift post TEST
# swift post test
# swift list -l
0 0 2014-05-14 07:06:33 TEST
0 0 2014-05-14 07:06:37 test
and then, using s3cmd listed container.
# s3cmd ls
2009-02-03 16:45 s3://TEST
2009-02-03 16:45 s3://test
Container creating date is shown 2009-02-03.
This is one bug.
In next, using s3cmd file upload to TEST container
# s3cmd put file1 s3://TEST
file1 -> s3://TEST/file1 [1 of 1]
801 of 801 100% in 6s 123.01 B/s done
this is no problem
but using s3cmd file update to test container, this failed.
# s3cmd put file1 s3://test
file1 -> s3://test/file1 [1 of 1]
801 of 801 100% in 0s 49.17 kB/s done
ERROR: S3 error: 403 (AccessDenied): Access denied
In case of lower case container, when i put using s3cmd, access deined error occured.
Hi, lee.
First one is related to https:/ /github. com/fujita/ swift3/ issues/ 61.
It is basically caused from swift's specification. To solve it, the swift command you reported makes HEAD requests for all containers before the response but current swift3 doesn't do so because it sacrifices its performance. However, my colleague is trying to fix it, right now. Please wait the activity.
The other seems not to be a swift3 bug because I can do that (possible to put an object against to both TEST and test containers) by s3curl. Could you show me the proxy log, version number and some information about s3cmd.
Best