)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"c5357f370d9ec818fadc478b203b6b71dafb0503","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Fix description for 204 response"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In addition to DELETE requests, keystone may return an HTTP 204 as a"},{"line_number":10,"context_line":"success code for PUT[1] and HEAD[2] requests. It would be quite"},{"line_number":11,"context_line":"disconcerting if keystone were actually deleting resources during such"},{"line_number":12,"context_line":"additive and read-only operations, so this patch simplifies the 204"},{"line_number":13,"context_line":"description so that it is truthful in all of its use cases."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5a22e58a_7cf6afd8","line":10,"range":{"start_line":10,"start_character":28,"end_line":10,"end_character":44},"updated":"2017-03-14 13:19:52.000000000","message":"this is true, but it is wrong. We should not return 204 as response from HEADs :)","commit_id":"37185428dd8689d14b3a02fca1e1b58eb75277f2"}]}