HEAD request over a container is not returning the ACL headers
Bug #879371 reported by
Juan J. Martínez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Object Storage (swift) |
Invalid
|
Undecided
|
Juan J. Martínez | ||
Bug Description
I've noticed this problem with 1.4.3, although I think it was introduced by the container sync code.
Steps to reproduce:
1. Set read and write ACL in a container
2. Get the container information
There should be two headers X-Container-Read and X-Container-Write (as in 1.4.0), but they're not present.
Please see attached test script.
Revision history for this message
| Juan J. Martínez (jjmartinez) wrote | #1 |
Revision history for this message
| Juan J. Martínez (jjmartinez) wrote | #2 |
Revision history for this message
| Juan J. Martínez (jjmartinez) wrote | #3 |
| Changed in swift: | |
| status: | New → Confirmed |
| assignee: | nobody → Juan J. Martínez (jjmartinez) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to swift (master) | #4 |
| Changed in swift: | |
| status: | Confirmed → In Progress |
| Changed in swift: | |
| status: | In Progress → Invalid |
To post a comment you must log in.
The code introducing the bug seems to be in swift/server/
These headers should persist. What do you think?
I'm attaching a patch that solves the problem, but I don't know id there's some kind of side effect.