)]}'
{"guidelines/http.rst":[{"author":{"_account_id":12000,"name":"Ian Cordasco","email":"sigmavirus24@gmail.com","username":"sigmavirus24"},"change_message_id":"2917c452e933a7d383bdd04797be10bccee00629","unresolved":false,"context_lines":[{"line_number":58,"context_line":""},{"line_number":59,"context_line":"* If an operation is disabled due to the configuration in a server side, the"},{"line_number":60,"context_line":"  return code should be **405 Method Not Allowed**. There was alternative code"},{"line_number":61,"context_line":"  **501 Not Implemented** for this situation, but we should not use it because"},{"line_number":62,"context_line":"  501 means the API method(POST/PUT, etc.) is not valid for any resource. So if"},{"line_number":63,"context_line":"  returning 501 on a particular URI and method, clients possibily misunderstand"},{"line_number":64,"context_line":"  that they can not use the method for all resources."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7a016987_6a033a0e","line":61,"updated":"2015-05-18 15:42:58.000000000","message":"I would change this to mean \"because the example says this can mean that the API method is not valid for any resource. Due to people commonly misreading RFCs, it is not ideal as some intermediaries may handle it incorrectly.\"","commit_id":"32b0b942d02c7dae58489c43328f4bdc64535478"},{"author":{"_account_id":1669,"name":"Julien Danjou","display_name":"jd","email":"julien@danjou.info","username":"jdanjou"},"change_message_id":"793a26e74aa5f447e66477a0367037c4106538dd","unresolved":false,"context_lines":[{"line_number":59,"context_line":"* If an operation is disabled due to the configuration in a server side, the"},{"line_number":60,"context_line":"  return code should be **405 Method Not Allowed**. There was alternative code"},{"line_number":61,"context_line":"  **501 Not Implemented** for this situation, but we should not use it because"},{"line_number":62,"context_line":"  501 means the API method(POST/PUT, etc.) is not valid for any resource. So if"},{"line_number":63,"context_line":"  returning 501 on a particular URI and method, clients possibily misunderstand"},{"line_number":64,"context_line":"  that they can not use the method for all resources."},{"line_number":65,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7a016987_16398f41","line":62,"updated":"2015-05-18 21:15:07.000000000","message":"501 is not tied only to request method. It is appropriate AFAICT to reply 501 if the server does not implement a feature.\n\n405 is however tied to a HTTP method not supported AFAICT.","commit_id":"32b0b942d02c7dae58489c43328f4bdc64535478"},{"author":{"_account_id":12606,"name":"Miguel Grinberg","email":"miguel.grinberg@gmail.com","username":"miguelgrinberg"},"change_message_id":"b9b662809f64d4f93c8d9f7e1e2f657d37ba99e4","unresolved":false,"context_lines":[{"line_number":59,"context_line":"* If an operation is disabled due to the configuration in a server side, the"},{"line_number":60,"context_line":"  return code should be **405 Method Not Allowed**. There was alternative code"},{"line_number":61,"context_line":"  **501 Not Implemented** for this situation, but we should not use it because"},{"line_number":62,"context_line":"  501 means the API method(POST/PUT, etc.) is not valid for any resource. So if"},{"line_number":63,"context_line":"  returning 501 on a particular URI and method, clients possibily misunderstand"},{"line_number":64,"context_line":"  that they can not use the method for all resources."},{"line_number":65,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7a016987_acc5ca3c","line":62,"in_reply_to":"7a016987_16398f41","updated":"2015-05-18 23:41:39.000000000","message":"Right, I agree with Julien\u0027s views. We are trying to find the most appropriate response code for something that clearly the HTTP specification does not cover. Clearly 405 Method Not Allowed is only about request methods, but 501 Not Implemented can be about other things. If it was only about methods it would have been named \"Method Not Implemented\".","commit_id":"32b0b942d02c7dae58489c43328f4bdc64535478"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"15974f052148e4215f94c3f9f5d932cab00886fd","unresolved":false,"context_lines":[{"line_number":59,"context_line":"* If an operation is disabled due to the configuration in a server side, the"},{"line_number":60,"context_line":"  return code should be **405 Method Not Allowed**. There was alternative code"},{"line_number":61,"context_line":"  **501 Not Implemented** for this situation, but we should not use it because"},{"line_number":62,"context_line":"  501 means the API method(POST/PUT, etc.) is not valid for any resource. So if"},{"line_number":63,"context_line":"  returning 501 on a particular URI and method, clients possibily misunderstand"},{"line_number":64,"context_line":"  that they can not use the method for all resources."},{"line_number":65,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa32b979_c04c2fa0","line":62,"in_reply_to":"7a016987_acc5ca3c","updated":"2015-06-24 19:55:29.000000000","message":"Are you aware of https://review.openstack.org/#/c/183456/9/guidelines/http.rst ?\n\nIt seems to be at odds with your suggestion to use 501 for \"not implemented feature\"","commit_id":"32b0b942d02c7dae58489c43328f4bdc64535478"},{"author":{"_account_id":13997,"name":"SHIGEMATSU Mitsuhiro","email":"shigematsu.mitsuhiro@lab.ntt.co.jp","username":"pshige"},"change_message_id":"cdcf1c1d0dddcd0f1f34a664baf069b6c0c39fd4","unresolved":false,"context_lines":[{"line_number":60,"context_line":"  return code should be **405 Method Not Allowed**. There was alternative code"},{"line_number":61,"context_line":"  **501 Not Implemented** for this situation, but we should not use it because"},{"line_number":62,"context_line":"  501 means the API method(POST/PUT, etc.) is not valid for any resource. So if"},{"line_number":63,"context_line":"  returning 501 on a particular URI and method, clients possibily misunderstand"},{"line_number":64,"context_line":"  that they can not use the method for all resources."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"HTTP Methods"}],"source_content_type":"text/x-rst","patch_set":3,"id":"da20952f_3449b631","line":63,"updated":"2015-09-05 13:41:11.000000000","message":"s/possibily/possibly/","commit_id":"32b0b942d02c7dae58489c43328f4bdc64535478"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"15974f052148e4215f94c3f9f5d932cab00886fd","unresolved":false,"context_lines":[{"line_number":61,"context_line":"  **501 Not Implemented** for this situation, but we should not use it because"},{"line_number":62,"context_line":"  501 means the API method(POST/PUT, etc.) is not valid for any resource. So if"},{"line_number":63,"context_line":"  returning 501 on a particular URI and method, clients possibily misunderstand"},{"line_number":64,"context_line":"  that they can not use the method for all resources."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"HTTP Methods"},{"line_number":67,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa32b979_40281f9a","line":64,"updated":"2015-06-24 19:55:29.000000000","message":"You can refer to the section on common mistakes (https://review.openstack.org/#/c/183456/9/guidelines/http.rst) for more details, assuming we do not agree instead that 501 is fine for feature not implemented.","commit_id":"32b0b942d02c7dae58489c43328f4bdc64535478"}]}