World readable access to segmented object produces 401, even if _segments is also world readable.
Bug #1082835 reported by
Byron McCollum
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Incomplete
|
Low
|
Alexey Khivin |
Bug Description
So, seems I've stumbled across something that used to work in Essex, but is no longer working in Folsom. Using the swift tool, upload a segmented object to a container with a `.r:*` read ACL. Accessing the object anonymously produces a 401 as expected, as the segments are in the companion _segments container. After giving `.r:*` access to the _segments container, anonymous access to the segmented object used to work. In Folsom, it continues to produce a 401.
Changed in swift: | |
assignee: | nobody → Madhuri Kumari (madhuri-rai07) |
Changed in swift: | |
assignee: | Madhuri Kumari (madhuri-rai07) → nobody |
Changed in swift: | |
assignee: | nobody → Alex Khivin (akhivin) |
Changed in swift: | |
importance: | High → Low |
To post a comment you must log in.
For the time being (ie until this bug is resolved either through a change in behavior or an update to the docs), enable .rlistings on the _segements container. This will allow the anonymous manifest requests to work.