)]}'
{"etc/proxy-server.conf-sample":[{"author":{"_account_id":6198,"name":"Peter Portante","email":"peter.a.portante@gmail.com","username":"peter-a-portante"},"change_message_id":"acf4aa48dfa9088e7fa87876d4237c5b4e44a71f","unresolved":false,"context_lines":[{"line_number":577,"context_line":""},{"line_number":578,"context_line":"[filter:read-only]"},{"line_number":579,"context_line":"use \u003d egg:swift#read_only"},{"line_number":580,"context_line":"# read_only_accounts \u003d test1,test2"},{"line_number":581,"context_line":"# Set this to comma separated list of accounts that you want to make read-only."}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAWH%2F%2BOjw%3D","line":580,"updated":"2014-03-28 09:07:11.000000000","message":"I think adding an X-Account-Readonly header on a POST could avoid having this in a configuration file?  Thoughts?","commit_id":"a7ecad0bd11190bdbab167f65f03d889aa9c6a31"},{"author":{"_account_id":8542,"name":"Prashanth Pai","email":"ppai@redhat.com","username":"pai"},"change_message_id":"3e1ffe3f82da25f92986af634f1c4b7b8cb0ea3a","unresolved":false,"context_lines":[{"line_number":577,"context_line":""},{"line_number":578,"context_line":"[filter:read-only]"},{"line_number":579,"context_line":"use \u003d egg:swift#read_only"},{"line_number":580,"context_line":"# read_only_accounts \u003d test1,test2"},{"line_number":581,"context_line":"# Set this to comma separated list of accounts that you want to make read-only."}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAWH%2F%2BN2g%3D","line":580,"in_reply_to":"AAAAWH%2F%2BOK4%3D","updated":"2014-03-28 10:54:14.000000000","message":"I have one little concern about the approach- the user roles(admin/reseller) do no exist when there is no auth middleware in pipeline.","commit_id":"a7ecad0bd11190bdbab167f65f03d889aa9c6a31"},{"author":{"_account_id":8542,"name":"Prashanth Pai","email":"ppai@redhat.com","username":"pai"},"change_message_id":"ee52a0cbc684730b4d9127bc3fff330b40b550e5","unresolved":false,"context_lines":[{"line_number":577,"context_line":""},{"line_number":578,"context_line":"[filter:read-only]"},{"line_number":579,"context_line":"use \u003d egg:swift#read_only"},{"line_number":580,"context_line":"# read_only_accounts \u003d test1,test2"},{"line_number":581,"context_line":"# Set this to comma separated list of accounts that you want to make read-only."}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAWH%2F%2BOK4%3D","line":580,"in_reply_to":"AAAAWH%2F%2BOS0%3D","updated":"2014-03-28 10:03:09.000000000","message":"Thanks! I just realized the account metadata are cached. I\u0027m currently looking at account_quotas filter as reference as it does something very similar :)","commit_id":"a7ecad0bd11190bdbab167f65f03d889aa9c6a31"},{"author":{"_account_id":6198,"name":"Peter Portante","email":"peter.a.portante@gmail.com","username":"peter-a-portante"},"change_message_id":"ca7d7198a12f66b6e8dc1a8de9611fa4ce9458d2","unresolved":false,"context_lines":[{"line_number":577,"context_line":""},{"line_number":578,"context_line":"[filter:read-only]"},{"line_number":579,"context_line":"use \u003d egg:swift#read_only"},{"line_number":580,"context_line":"# read_only_accounts \u003d test1,test2"},{"line_number":581,"context_line":"# Set this to comma separated list of accounts that you want to make read-only."}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAWH%2F%2BOS0%3D","line":580,"in_reply_to":"AAAAWH%2F%2BOeo%3D","updated":"2014-03-28 09:49:04.000000000","message":"Regarding Account ACLs, I think it does, though I have not reviewed that code in detail.\n\nThe read-only filter will have to live after any authentication middleware in the pipeline, I would think, to avoid revealing any information about the account state to unauthorized requests.  Such authentication middleware will already cause the account metadata to be pulled and cached during the authorization checks by the proxy-server. So this added check will either use the existing cached values, or just do the proxy-server a favor of fetching the data for the account ahead of time.\n\nIn the absence of authentication middleware, the proxy-server makes existence checks on containers and accounts, which cache the account information along with it. So for the same reason above, fetching the account information ahead of time should not be a problem.\n\nRegarding who will have the rights to change it, I would think the same person who had the rights to change the conf file, the admin.  At least, I would suggest starting there.","commit_id":"a7ecad0bd11190bdbab167f65f03d889aa9c6a31"},{"author":{"_account_id":8542,"name":"Prashanth Pai","email":"ppai@redhat.com","username":"pai"},"change_message_id":"b5ca5bed726eb31471434b99d6efeb9bec69b979","unresolved":false,"context_lines":[{"line_number":577,"context_line":""},{"line_number":578,"context_line":"[filter:read-only]"},{"line_number":579,"context_line":"use \u003d egg:swift#read_only"},{"line_number":580,"context_line":"# read_only_accounts \u003d test1,test2"},{"line_number":581,"context_line":"# Set this to comma separated list of accounts that you want to make read-only."}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAWH%2F%2BOeo%3D","line":580,"in_reply_to":"AAAAWH%2F%2BOjw%3D","updated":"2014-03-28 09:25:44.000000000","message":"Good point. But if it is stored as metadata in account DB entry, the filter has to retrieve it first (may be by get_account_info but never the less, an additional call).  Also, who(user/admin/reseller) will have the rights to set or remove  X-Account-Readonly ? Account ACLs (https://blueprints.launchpad.net/swift/+spec/account-acls) might do something close to what you are suggesting ?","commit_id":"a7ecad0bd11190bdbab167f65f03d889aa9c6a31"}]}
