Cannot upload an object with DragonDisk

[firejun]

I can't upload files to the same name as the bucket is attached to the top.

• What steps will reproduce the problem?
  1. LeoFS server is 'All-in-one-server' (Environment is default)
  2. Create a user => 'leofs'
  3. Add a bucket => 'leofs'
  4. Upload a file => '_leofs.txt', 'aleofs.txt', '1leofs.txt'
     This is sccuess pattern.
  5. Upload a file => 'leofs.txt', 'leofs_.txt', 'leofs1.txt'
     This is fail pattern.
• What is the expected output?
  File upload is success.
• What do you see instead?
  File upload is fail.
• Which compiler are you using?
  Erlang R16B02
• Which operating system and revision are you using?
  OS : CentOS 6.3(64bit)
  LeoFS : 0.16.0
  DragonDisk: 1.05(Windows7)

*** http output log ***

-This is fail pattern.
[DragonDisk request]
HEAD /test.rpm HTTP/1.1
Host: test.leofs.org
Date: Wed, 06 Nov 2013 07:31:09 GMT
Authorization: AWS 35c44f339e7454ac6290:OMASO9rKTFNf1I9RefKhcXg4/OU=
Connection: Keep-Alive
User-Agent: DragonDisk 1.05 ( http://www.dragondisk.com )

[LeoFS response]
HTTP/1.1 403 Forbidden
connection: keep-alive
date: Wed, 06 Nov 2013 07:35:26 GMT
content-length: 0
server: LeoFS

-This is success pattern.
[DragonDisk request]
HEAD /_test.rpm HTTP/1.1
Host: test.leofs.org
Date: Wed, 06 Nov 2013 07:34:05 GMT
Authorization: AWS 35c44f339e7454ac6290:C3BraV8xEehyEG1GFZUX6HgBji4=
Connection: Keep-Alive
User-Agent: DragonDisk 1.05 ( http://www.dragondisk.com )

[LeoFS response]
HTTP/1.1 404 Not Found
connection: keep-alive
date: Wed, 06 Nov 2013 07:37:43 GMT
content-length: 0
server: LeoFS

[firejun]

get-endpoints
endpoint | created at
-----------------+---------------------------
s3.amazonaws.com | 2013-11-06 14:46:57 +0900
leofs.org | 2013-11-06 14:48:13 +0900
localhost | 2013-11-06 14:46:57 +0900

status
[System config]
system version : 0.16.0
total replicas : 1
# of successes of R : 1
# of successes of W : 1
# of successes of D : 1

of DC-awareness replicas : 0

of Rack-awareness replicas : 0

                 ring size : 2^128
          ring hash (cur)  : d84febcf
          ring hash (prev) : d84febcf

[Node(s) state]

---

type node state ring (cur) ring (prev) when

---

S storage_0@127.0.0.1 running d84febcf d84febcf 2013-11-06 14:47:19 +0900
G gateway_0@127.0.0.1 running d84febcf d84febcf 2013-11-06 16:37:40 +0900

[yosukehara]

Thank you for posting this issue.
We have found this problem. We will resolve it, soon.

[firejun]

Thank you so much!!

[mocchira]

@firejun Could you confirm if this issue is solved?

[firejun]

I confirmed that this issue is solved.
Thank you very much!!