)]}'
{"guidelines/http.rst":[{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"caf1eda0c744db00d25d651da9c2f14f915ee206","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"The HTTP RFC is a quite large specification. The HTTP 1.1"},{"line_number":7,"context_line":"specification [RFC 2616](https://tools.ietf.org/html/rfc2616) clocks"},{"line_number":8,"context_line":"in at 175 pages. Published in 1999 it assumes a certain use of the"},{"line_number":9,"context_line":"HTTP protocol in the web browser / server framework. The idea for the"},{"line_number":10,"context_line":"use of HTTP as a more generic API layer only emerged a year after the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5ad58531_81ceca81","line":7,"updated":"2015-05-11 21:25:13.000000000","message":"There\u0027s a pending change which (rightly so) is updating pointers to 2616 to the 723* series: https://review.openstack.org/#/c/177445/\n\nBesides cranking up the page numbers nicely it has some other good bits.","commit_id":"62e627645a6cd0653f17eec2c243280a3e5826fe"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"b758cf1e67e145c3791a8d1f8a4f9924e976b0f1","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"The HTTP RFC is a quite large specification. The HTTP 1.1"},{"line_number":7,"context_line":"specification [RFC 2616](https://tools.ietf.org/html/rfc2616) clocks"},{"line_number":8,"context_line":"in at 175 pages. Published in 1999 it assumes a certain use of the"},{"line_number":9,"context_line":"HTTP protocol in the web browser / server framework. The idea for the"},{"line_number":10,"context_line":"use of HTTP as a more generic API layer only emerged a year after the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a0c5dc1_ae776dd3","line":7,"in_reply_to":"5ad58531_81ceca81","updated":"2015-05-12 13:35:45.000000000","message":"So... do we change this to \"the original HTTP RFC\", then reference the break out parts below? Because I feel like you can\u0027t set context with the big list of changes.","commit_id":"62e627645a6cd0653f17eec2c243280a3e5826fe"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"529a596042e1ea68113c3995387b7f0221f3a911","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"The HTTP RFC is a quite large specification. The HTTP 1.1"},{"line_number":7,"context_line":"specification [RFC 2616](https://tools.ietf.org/html/rfc2616) clocks"},{"line_number":8,"context_line":"in at 175 pages. Published in 1999 it assumes a certain use of the"},{"line_number":9,"context_line":"HTTP protocol in the web browser / server framework. The idea for the"},{"line_number":10,"context_line":"use of HTTP as a more generic API layer only emerged a year after the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a0c5dc1_753598d8","line":7,"in_reply_to":"9a0c5dc1_ae776dd3","updated":"2015-05-13 10:24:21.000000000","message":"Yeah, for the sake of setting historical context, linking to 2616 here seems right.","commit_id":"62e627645a6cd0653f17eec2c243280a3e5826fe"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"529a596042e1ea68113c3995387b7f0221f3a911","unresolved":false,"context_lines":[{"line_number":12,"context_line":"thesis](https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm)"},{"line_number":13,"context_line":"and was not widely adopted until many years later."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"As such, it\u0027s important to realize the concepts and constructs that we"},{"line_number":16,"context_line":"are trying to get out of HTTP are not a perfect match. While there"},{"line_number":17,"context_line":"might be clearly wrong usage of HTTP, there end up being grey areas"},{"line_number":18,"context_line":"when mapping our needs on top of this protocol. As such, any"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a0c5dc1_75aeb886","line":15,"updated":"2015-05-13 10:24:21.000000000","message":"Try the following on for size:\n\nIt\u0027s important to realize that concepts and constructs that we want to manipulate in any given system will not be a perfect match with the concepts and constraints of HTTP. These mismatches can indicate a clearly wrong usage HTTP, a special case to meet requirements or an opportunity to improve an existing design. Any recommendation about using HTTP should come with...[keep the rest]","commit_id":"62e627645a6cd0653f17eec2c243280a3e5826fe"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"1817cbdf4607996632e08ed6c584dd7447d2f49b","unresolved":false,"context_lines":[{"line_number":12,"context_line":"thesis](https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm)"},{"line_number":13,"context_line":"and was not widely adopted until many years later."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"As such, it\u0027s important to realize the concepts and constructs that we"},{"line_number":16,"context_line":"are trying to get out of HTTP are not a perfect match. While there"},{"line_number":17,"context_line":"might be clearly wrong usage of HTTP, there end up being grey areas"},{"line_number":18,"context_line":"when mapping our needs on top of this protocol. As such, any"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7a016987_d82c88ad","line":15,"in_reply_to":"9a0c5dc1_75aeb886","updated":"2015-05-15 09:38:52.000000000","message":"Done","commit_id":"62e627645a6cd0653f17eec2c243280a3e5826fe"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"39a87663affe6321be952c5af11139c123298f77","unresolved":false,"context_lines":[{"line_number":17,"context_line":"might be clearly wrong usage of HTTP, there end up being grey areas"},{"line_number":18,"context_line":"when mapping our needs on top of this protocol. As such, any"},{"line_number":19,"context_line":"recommendation about using HTTP should come with substantial"},{"line_number":20,"context_line":"explaination about why that\u0027s the best approach that we can determine"},{"line_number":21,"context_line":"at this time. This provides the justification for the decision in the"},{"line_number":22,"context_line":"present, and bread crumbs in the future if that justification no"},{"line_number":23,"context_line":"longer holds."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a0c5dc1_0055134f","line":20,"updated":"2015-05-12 20:41:55.000000000","message":"s/explaination/explanation/","commit_id":"62e627645a6cd0653f17eec2c243280a3e5826fe"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"1817cbdf4607996632e08ed6c584dd7447d2f49b","unresolved":false,"context_lines":[{"line_number":17,"context_line":"might be clearly wrong usage of HTTP, there end up being grey areas"},{"line_number":18,"context_line":"when mapping our needs on top of this protocol. As such, any"},{"line_number":19,"context_line":"recommendation about using HTTP should come with substantial"},{"line_number":20,"context_line":"explaination about why that\u0027s the best approach that we can determine"},{"line_number":21,"context_line":"at this time. This provides the justification for the decision in the"},{"line_number":22,"context_line":"present, and bread crumbs in the future if that justification no"},{"line_number":23,"context_line":"longer holds."}],"source_content_type":"text/x-rst","patch_set":1,"id":"7a016987_b818ac85","line":20,"in_reply_to":"9a0c5dc1_0055134f","updated":"2015-05-15 09:38:52.000000000","message":"Done","commit_id":"62e627645a6cd0653f17eec2c243280a3e5826fe"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"39a87663affe6321be952c5af11139c123298f77","unresolved":false,"context_lines":[{"line_number":20,"context_line":"explaination about why that\u0027s the best approach that we can determine"},{"line_number":21,"context_line":"at this time. This provides the justification for the decision in the"},{"line_number":22,"context_line":"present, and bread crumbs in the future if that justification no"},{"line_number":23,"context_line":"longer holds."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"HTTP defines a set of standard headers, content negotiation with mime"},{"line_number":26,"context_line":"types, well defined status codes, a url structure, and methods on such"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a0c5dc1_a0aac76e","line":23,"updated":"2015-05-12 20:41:55.000000000","message":"big +1 for representing the reason.\n\nWe are going to implement/change APIs based on this guideline. If the guideline contains enough explanation, we can avoid the update of the guideline and avoid affecting APIs of OpenStack projects.","commit_id":"62e627645a6cd0653f17eec2c243280a3e5826fe"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"39a87663affe6321be952c5af11139c123298f77","unresolved":false,"context_lines":[{"line_number":28,"context_line":""},{"line_number":29,"context_line":"If something is not covered by this document, or seems ambiguous after"},{"line_number":30,"context_line":"looking at these guidelines, implementers are encouraged to start a"},{"line_number":31,"context_line":"mailing list thread for clarity and to help make these guidelines more"},{"line_number":32,"context_line":"clear in the future."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"HTTP Response Codes"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a0c5dc1_60e28fd7","line":31,"updated":"2015-05-12 20:41:55.000000000","message":"nit s/clarify/clarifying/","commit_id":"62e627645a6cd0653f17eec2c243280a3e5826fe"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"1817cbdf4607996632e08ed6c584dd7447d2f49b","unresolved":false,"context_lines":[{"line_number":28,"context_line":""},{"line_number":29,"context_line":"If something is not covered by this document, or seems ambiguous after"},{"line_number":30,"context_line":"looking at these guidelines, implementers are encouraged to start a"},{"line_number":31,"context_line":"mailing list thread for clarity and to help make these guidelines more"},{"line_number":32,"context_line":"clear in the future."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"HTTP Response Codes"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7a016987_981df075","line":31,"in_reply_to":"9a0c5dc1_60e28fd7","updated":"2015-05-15 09:38:52.000000000","message":"Done","commit_id":"62e627645a6cd0653f17eec2c243280a3e5826fe"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"529a596042e1ea68113c3995387b7f0221f3a911","unresolved":false,"context_lines":[{"line_number":29,"context_line":"If something is not covered by this document, or seems ambiguous after"},{"line_number":30,"context_line":"looking at these guidelines, implementers are encouraged to start a"},{"line_number":31,"context_line":"mailing list thread for clarity and to help make these guidelines more"},{"line_number":32,"context_line":"clear in the future."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"HTTP Response Codes"},{"line_number":35,"context_line":"-------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a0c5dc1_55ba940b","line":32,"updated":"2015-05-13 10:24:21.000000000","message":"I think the intent of the statement \"If something is not covered by this document, projects should follow [the rfc]\" that was remove needs to put back in so that the order of investigation is:\n\n* guidelines\n* rfc[s]\n* mailing list","commit_id":"62e627645a6cd0653f17eec2c243280a3e5826fe"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"1817cbdf4607996632e08ed6c584dd7447d2f49b","unresolved":false,"context_lines":[{"line_number":29,"context_line":"If something is not covered by this document, or seems ambiguous after"},{"line_number":30,"context_line":"looking at these guidelines, implementers are encouraged to start a"},{"line_number":31,"context_line":"mailing list thread for clarity and to help make these guidelines more"},{"line_number":32,"context_line":"clear in the future."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"HTTP Response Codes"},{"line_number":35,"context_line":"-------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7a016987_3314dd42","line":32,"in_reply_to":"9a0c5dc1_55ba940b","updated":"2015-05-15 09:38:52.000000000","message":"I will give the counter example of https://review.openstack.org/#/c/181283/ as why I think the order of people reading this document should be\n\n * guidelines\n * mailing list (after consulting rfc)","commit_id":"62e627645a6cd0653f17eec2c243280a3e5826fe"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"39a87663affe6321be952c5af11139c123298f77","unresolved":false,"context_lines":[{"line_number":42,"context_line":"* 3xx: redirection (the resource is at another location, or is"},{"line_number":43,"context_line":"  unchanged since last requested)"},{"line_number":44,"context_line":"* 4xx: client errors (the client did something wrong)"},{"line_number":45,"context_line":"* 5xx: server serrors (the server failed in a way that was unexpected)"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"2xx Success Codes"},{"line_number":48,"context_line":"~~~~~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a0c5dc1_8088e323","line":45,"updated":"2015-05-12 20:41:55.000000000","message":"s/serrors/errors/","commit_id":"62e627645a6cd0653f17eec2c243280a3e5826fe"},{"author":{"_account_id":12321,"name":"Ryan Brown","email":"rybrown@redhat.com","username":"ryansb"},"change_message_id":"20de4c63e82c65910a594436ba59fd6cbb5dd554","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"The HTTP RFC is a quite large specification. The HTTP 1.1"},{"line_number":7,"context_line":"specification [RFC 2616](https://tools.ietf.org/html/rfc2616) clocks"},{"line_number":8,"context_line":"in at 175 pages. Published in 1999 it assumes a certain use of the"},{"line_number":9,"context_line":"HTTP protocol in the web browser / server framework. The idea for the"},{"line_number":10,"context_line":"use of HTTP as a more generic API layer only emerged a year after the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a016987_31bbb2e7","line":7,"updated":"2015-05-15 12:38:13.000000000","message":"In other places we\u0027ve referenced 7230-7235 (see https://www.mnot.net/blog/2014/06/07/rfc2616_is_dead). Can we standardize on that?","commit_id":"07af1f24f7d04ab2350eafc3635b60b4986871ae"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"7faa211d215b351885781f3191cb70a3ac7b449c","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"The HTTP RFC is a quite large specification. The HTTP 1.1"},{"line_number":7,"context_line":"specification [RFC 2616](https://tools.ietf.org/html/rfc2616) clocks"},{"line_number":8,"context_line":"in at 175 pages. Published in 1999 it assumes a certain use of the"},{"line_number":9,"context_line":"HTTP protocol in the web browser / server framework. The idea for the"},{"line_number":10,"context_line":"use of HTTP as a more generic API layer only emerged a year after the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a016987_d7cd6eb8","line":7,"in_reply_to":"7a016987_31bbb2e7","updated":"2015-05-15 13:26:15.000000000","message":"see discussion between cdent and I in PS 1. The important part of this includes a time line. While the spec has a more recent rev with minor clarifications, HTTP 1.1 saw all it\u0027s actually changes prior to the use of HTTP as a generic web services layer. So I think in the background portion, rfc2616 reference is important.\n\nI think other call outs to relevant sections are good when appropriate, mostly 7231.","commit_id":"07af1f24f7d04ab2350eafc3635b60b4986871ae"},{"author":{"_account_id":12321,"name":"Ryan Brown","email":"rybrown@redhat.com","username":"ryansb"},"change_message_id":"2a82e010cf3df895262969f0ef9a2a11e2be9346","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"The HTTP RFC is a quite large specification. The HTTP 1.1"},{"line_number":7,"context_line":"specification [RFC 2616](https://tools.ietf.org/html/rfc2616) clocks"},{"line_number":8,"context_line":"in at 175 pages. Published in 1999 it assumes a certain use of the"},{"line_number":9,"context_line":"HTTP protocol in the web browser / server framework. The idea for the"},{"line_number":10,"context_line":"use of HTTP as a more generic API layer only emerged a year after the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a016987_979ff64f","line":7,"in_reply_to":"7a016987_d7cd6eb8","updated":"2015-05-15 13:31:57.000000000","message":"Ok, makes sense to me.","commit_id":"07af1f24f7d04ab2350eafc3635b60b4986871ae"},{"author":{"_account_id":12321,"name":"Ryan Brown","email":"rybrown@redhat.com","username":"ryansb"},"change_message_id":"2a82e010cf3df895262969f0ef9a2a11e2be9346","unresolved":false,"context_lines":[{"line_number":9,"context_line":"HTTP protocol in the web browser / server framework. The idea for the"},{"line_number":10,"context_line":"use of HTTP as a more generic API layer only emerged a year after the"},{"line_number":11,"context_line":"publication of HTTP 1.1 in [Chapter 5 of Roy Fieldings PhD"},{"line_number":12,"context_line":"thesis](https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm)"},{"line_number":13,"context_line":"and was not widely adopted until many years later."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"It\u0027s important to realize that concepts and constructs that we want to"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a016987_77c59a3a","line":12,"updated":"2015-05-15 13:31:57.000000000","message":"This is a markdown link, and won\u0027t render right in RST.","commit_id":"07af1f24f7d04ab2350eafc3635b60b4986871ae"},{"author":{"_account_id":10670,"name":"Michael McCune","email":"elmiko@redhat.com","username":"mimccune"},"change_message_id":"c5bc966b7f802d62a93e6daa1f125951098b2b42","unresolved":false,"context_lines":[{"line_number":15,"context_line":"It\u0027s important to realize that concepts and constructs that we want to"},{"line_number":16,"context_line":"manipulate in any given system will not be a perfect match with the"},{"line_number":17,"context_line":"concepts and constraints of HTTP. These mismatches can indicate a"},{"line_number":18,"context_line":"clearly wrong usage HTTP, a special case to meet requirements, or an"},{"line_number":19,"context_line":"opportunity to improve an existing design. Any recommendation about"},{"line_number":20,"context_line":"using HTTP should come with substantial explanation about why that\u0027s"},{"line_number":21,"context_line":"the best approach that we can determine at this time. This provides"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7a016987_1d2fa7f7","line":18,"updated":"2015-05-15 14:13:07.000000000","message":"s/usage HTTP/usage of HTTP/","commit_id":"4cf22f2a3fa56d46ffbdb709bc529d64a7ef596e"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"86b08c210744fabd5176e2dc09bd27dbb7973f8c","unresolved":false,"context_lines":[{"line_number":15,"context_line":"It\u0027s important to realize that concepts and constructs that we want to"},{"line_number":16,"context_line":"manipulate in any given system will not be a perfect match with the"},{"line_number":17,"context_line":"concepts and constraints of HTTP. These mismatches can indicate a"},{"line_number":18,"context_line":"clearly wrong usage HTTP, a special case to meet requirements, or an"},{"line_number":19,"context_line":"opportunity to improve an existing design. Any recommendation about"},{"line_number":20,"context_line":"using HTTP should come with substantial explanation about why that\u0027s"},{"line_number":21,"context_line":"the best approach that we can determine at this time. This provides"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7a016987_abd726be","line":18,"in_reply_to":"7a016987_1d2fa7f7","updated":"2015-05-15 15:55:30.000000000","message":"Done","commit_id":"4cf22f2a3fa56d46ffbdb709bc529d64a7ef596e"},{"author":{"_account_id":10670,"name":"Michael McCune","email":"elmiko@redhat.com","username":"mimccune"},"change_message_id":"c5bc966b7f802d62a93e6daa1f125951098b2b42","unresolved":false,"context_lines":[{"line_number":18,"context_line":"clearly wrong usage HTTP, a special case to meet requirements, or an"},{"line_number":19,"context_line":"opportunity to improve an existing design. Any recommendation about"},{"line_number":20,"context_line":"using HTTP should come with substantial explanation about why that\u0027s"},{"line_number":21,"context_line":"the best approach that we can determine at this time. This provides"},{"line_number":22,"context_line":"the justification for the decision in the present, and bread crumbs in"},{"line_number":23,"context_line":"the future if that justification no longer holds."},{"line_number":24,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7a016987_3d1383ba","line":21,"updated":"2015-05-15 14:13:07.000000000","message":"s/this time/the time/","commit_id":"4cf22f2a3fa56d46ffbdb709bc529d64a7ef596e"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"86b08c210744fabd5176e2dc09bd27dbb7973f8c","unresolved":false,"context_lines":[{"line_number":18,"context_line":"clearly wrong usage HTTP, a special case to meet requirements, or an"},{"line_number":19,"context_line":"opportunity to improve an existing design. Any recommendation about"},{"line_number":20,"context_line":"using HTTP should come with substantial explanation about why that\u0027s"},{"line_number":21,"context_line":"the best approach that we can determine at this time. This provides"},{"line_number":22,"context_line":"the justification for the decision in the present, and bread crumbs in"},{"line_number":23,"context_line":"the future if that justification no longer holds."},{"line_number":24,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7a016987_6be12e9a","line":21,"in_reply_to":"7a016987_3d1383ba","updated":"2015-05-15 15:55:30.000000000","message":"Done","commit_id":"4cf22f2a3fa56d46ffbdb709bc529d64a7ef596e"},{"author":{"_account_id":10670,"name":"Michael McCune","email":"elmiko@redhat.com","username":"mimccune"},"change_message_id":"c5bc966b7f802d62a93e6daa1f125951098b2b42","unresolved":false,"context_lines":[{"line_number":30,"context_line":"looking at these guidelines, implementers are encouraged to start a"},{"line_number":31,"context_line":"mailing list thread (with references to what they believe are relevant"},{"line_number":32,"context_line":"RFC sections) to clarify and to help make these guidelines more clear"},{"line_number":33,"context_line":"in the future. However, like legal code, and RFC is only a starting"},{"line_number":34,"context_line":"point. Precedents and common usage shape what an active standard"},{"line_number":35,"context_line":"really means."},{"line_number":36,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7a016987_fd83abca","line":33,"updated":"2015-05-15 14:13:07.000000000","message":"s/and RFC/an RFC/","commit_id":"4cf22f2a3fa56d46ffbdb709bc529d64a7ef596e"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"86b08c210744fabd5176e2dc09bd27dbb7973f8c","unresolved":false,"context_lines":[{"line_number":30,"context_line":"looking at these guidelines, implementers are encouraged to start a"},{"line_number":31,"context_line":"mailing list thread (with references to what they believe are relevant"},{"line_number":32,"context_line":"RFC sections) to clarify and to help make these guidelines more clear"},{"line_number":33,"context_line":"in the future. However, like legal code, and RFC is only a starting"},{"line_number":34,"context_line":"point. Precedents and common usage shape what an active standard"},{"line_number":35,"context_line":"really means."},{"line_number":36,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7a016987_4bef9287","line":33,"in_reply_to":"7a016987_fd83abca","updated":"2015-05-15 15:55:30.000000000","message":"Done","commit_id":"4cf22f2a3fa56d46ffbdb709bc529d64a7ef596e"},{"author":{"_account_id":12321,"name":"Ryan Brown","email":"rybrown@redhat.com","username":"ryansb"},"change_message_id":"2f7edb2fb8804fadc18578361a82dabd30d538b9","unresolved":false,"context_lines":[{"line_number":42,"context_line":"`7234 \u003chttps://tools.ietf.org/html/rfc7234\u003e`_, and"},{"line_number":43,"context_line":"`7235 \u003chttps://tools.ietf.org/html/rfc7235\u003e`_. No major functional"},{"line_number":44,"context_line":"changes are in these documents, but they are just reorganized for"},{"line_number":45,"context_line":"readability, and small clarifying corrections were made."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"HTTP Response Codes"},{"line_number":48,"context_line":"-------------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"7a016987_c786b864","line":45,"updated":"2015-05-17 19:55:17.000000000","message":"Thank\u0027s for calling these out.","commit_id":"49597bd0d5134cfdec3b3e050583c7fcff1df054"},{"author":{"_account_id":10670,"name":"Michael McCune","email":"elmiko@redhat.com","username":"mimccune"},"change_message_id":"1edff057305af0c451dbd29761577114191c344c","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"The HTTP RFC is a quite large specification. The HTTP 1.1"},{"line_number":7,"context_line":"specification `RFC 2616 \u003chttps://tools.ietf.org/html/rfc2616\u003e`_ clocks"},{"line_number":8,"context_line":"in at 175 pages. Published in 1999 it assumes a certain use of the"},{"line_number":9,"context_line":"HTTP protocol in the web browser / server framework. The idea for the"},{"line_number":10,"context_line":"use of HTTP as a more generic API layer only emerged a year after the"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3afb71cf_df4b2386","line":7,"updated":"2015-06-08 20:19:58.000000000","message":"should probably use the rfc directive here, so \":rfc:`2616`\"","commit_id":"8a6f61b243fafd7fc10164c085797cd6586ebe45"},{"author":{"_account_id":10670,"name":"Michael McCune","email":"elmiko@redhat.com","username":"mimccune"},"change_message_id":"1edff057305af0c451dbd29761577114191c344c","unresolved":false,"context_lines":[{"line_number":40,"context_line":"`7232 \u003chttps://tools.ietf.org/html/rfc7232\u003e`_,"},{"line_number":41,"context_line":"`7233 \u003chttps://tools.ietf.org/html/rfc7233\u003e`_,"},{"line_number":42,"context_line":"`7234 \u003chttps://tools.ietf.org/html/rfc7234\u003e`_, and"},{"line_number":43,"context_line":"`7235 \u003chttps://tools.ietf.org/html/rfc7235\u003e`_. No major functional"},{"line_number":44,"context_line":"changes are in these documents, but they are just reorganized for"},{"line_number":45,"context_line":"readability, and small clarifying corrections were made."},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"3afb71cf_eaea9f0e","line":43,"updated":"2015-06-08 20:19:58.000000000","message":"same as above, i think we should use the rfc directive","commit_id":"8a6f61b243fafd7fc10164c085797cd6586ebe45"},{"author":{"_account_id":4190,"name":"lifeless","email":"robertc@robertcollins.net","username":"lifeless"},"change_message_id":"507895ce28e8ae424c80ab36085a68dfa8afc1bf","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"The HTTP RFC is a quite large specification. The HTTP 1.1"},{"line_number":7,"context_line":"specification :rfc:`2616` clocks in at 175 pages. Published in"},{"line_number":8,"context_line":"1999 it assumes a certain use of the HTTP protocol in the web browser"},{"line_number":9,"context_line":"/ server framework. The idea for the use of HTTP as a more generic API"},{"line_number":10,"context_line":"layer only emerged a year after the publication of HTTP 1.1 in"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_9de9e6b9","line":7,"updated":"2015-06-23 21:53:15.000000000","message":"2616 isn\u0027t the spec anymore. http://www.rfc-editor.org/rfc/rfc7230.txt is the spec. I realise there\u0027s a note below, but I think its confusing to link people to a document they shouldn\u0027t read anymore. 7230 has internal links to the other components, and while as you say \u0027no major functional changes\u0027 - its actually quite different in detailed recommendations particularly, so well worth avoiding the confusion IMO.","commit_id":"ea36338c481e87d1c29ff6498fa606339eb2a2f2"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"2edaf734a8fcc90d5ac3cfcecab97bc160761bfe","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"The HTTP RFC is a quite large specification. The HTTP 1.1"},{"line_number":7,"context_line":"specification :rfc:`2616` clocks in at 175 pages. Published in"},{"line_number":8,"context_line":"1999 it assumes a certain use of the HTTP protocol in the web browser"},{"line_number":9,"context_line":"/ server framework. The idea for the use of HTTP as a more generic API"},{"line_number":10,"context_line":"layer only emerged a year after the publication of HTTP 1.1 in"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_bb2cf202","line":7,"in_reply_to":"fa32b979_9de9e6b9","updated":"2015-06-23 22:45:02.000000000","message":"When I read this guideline I thought the reference to RFC2616 was given for historical purposes.","commit_id":"ea36338c481e87d1c29ff6498fa606339eb2a2f2"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"cc8f4b749c76cc1bf2bf8bd1d5d31cdf2df167ab","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"The HTTP RFC is a quite large specification. The HTTP 1.1"},{"line_number":7,"context_line":"specification :rfc:`2616` clocks in at 175 pages. Published in"},{"line_number":8,"context_line":"1999 it assumes a certain use of the HTTP protocol in the web browser"},{"line_number":9,"context_line":"/ server framework. The idea for the use of HTTP as a more generic API"},{"line_number":10,"context_line":"layer only emerged a year after the publication of HTTP 1.1 in"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_acea760d","line":7,"in_reply_to":"fa32b979_bb2cf202","updated":"2015-06-24 00:12:33.000000000","message":"@lifeless, you can look at the conversation in the previous revisions. This is historical reference, the new http rfcs are referenced later.","commit_id":"ea36338c481e87d1c29ff6498fa606339eb2a2f2"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"2edaf734a8fcc90d5ac3cfcecab97bc160761bfe","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"*Note:* in recent years :rfc:`2616` was split into a multipart"},{"line_number":38,"context_line":"document in :rfc:`7230`, :rfc:`7231`, :rfc:`7232`, :rfc:`7233`,"},{"line_number":39,"context_line":":rfc:`7234`, and :rfc:`7235`.  No major functional changes are in"},{"line_number":40,"context_line":"these documents, but they are just reorganized for readability, and"},{"line_number":41,"context_line":"small clarifying corrections were made."},{"line_number":42,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_1b495eb7","line":39,"updated":"2015-06-23 22:45:02.000000000","message":"I know that the bulk of what really matters for HTTP/1.1 is in RFC 7230, but why would that make it \"THE\" spec? are RFC[7231:7235] the ugly siblings?","commit_id":"ea36338c481e87d1c29ff6498fa606339eb2a2f2"},{"author":{"_account_id":4190,"name":"lifeless","email":"robertc@robertcollins.net","username":"lifeless"},"change_message_id":"507895ce28e8ae424c80ab36085a68dfa8afc1bf","unresolved":false,"context_lines":[{"line_number":46,"context_line":"HTTP defines a set of standard response codes on requests, they are"},{"line_number":47,"context_line":"largely grouped as follows:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"* 1xx: compatibility with older HTTP, typically of no concern"},{"line_number":50,"context_line":"* 2xx: success"},{"line_number":51,"context_line":"* 3xx: redirection (the resource is at another location, or is"},{"line_number":52,"context_line":"  unchanged since last requested)"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_5dda7ee9","line":49,"updated":"2015-06-23 21:53:15.000000000","message":"This is misleading: 1xx is 1.1 and 2.0 only. I quote from http://tools.ietf.org/html/rfc1945#section-9.1 \"HTTP/1.0 does not define any 1xx status\n   codes and they are not a valid response to a HTTP/1.0 request.\"\n\n1xx is of great concern for correct operation when a 1.1+ request is received.","commit_id":"ea36338c481e87d1c29ff6498fa606339eb2a2f2"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"cc8f4b749c76cc1bf2bf8bd1d5d31cdf2df167ab","unresolved":false,"context_lines":[{"line_number":46,"context_line":"HTTP defines a set of standard response codes on requests, they are"},{"line_number":47,"context_line":"largely grouped as follows:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"* 1xx: compatibility with older HTTP, typically of no concern"},{"line_number":50,"context_line":"* 2xx: success"},{"line_number":51,"context_line":"* 3xx: redirection (the resource is at another location, or is"},{"line_number":52,"context_line":"  unchanged since last requested)"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_6c3eae8c","line":49,"in_reply_to":"fa32b979_5dda7ee9","updated":"2015-06-24 00:12:33.000000000","message":"Honestly, there is plenty of existing confusion. This document is meant as a primer for what people will write in python code. 1xx should remain \"typically of no concern\" for openstack application writers.","commit_id":"ea36338c481e87d1c29ff6498fa606339eb2a2f2"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"2edaf734a8fcc90d5ac3cfcecab97bc160761bfe","unresolved":false,"context_lines":[{"line_number":46,"context_line":"HTTP defines a set of standard response codes on requests, they are"},{"line_number":47,"context_line":"largely grouped as follows:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"* 1xx: compatibility with older HTTP, typically of no concern"},{"line_number":50,"context_line":"* 2xx: success"},{"line_number":51,"context_line":"* 3xx: redirection (the resource is at another location, or is"},{"line_number":52,"context_line":"  unchanged since last requested)"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_fbc11a30","line":49,"in_reply_to":"fa32b979_5dda7ee9","updated":"2015-06-23 22:45:02.000000000","message":"I agree with lifeless in terms of interpretation of the HTTP standard, but I also I see these response code as not something the typical openstack server would return.\n\nBut since this is supposed to be a generic section, perhaps we should amend.","commit_id":"ea36338c481e87d1c29ff6498fa606339eb2a2f2"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"6f774533147a44a9f945bb71fff5cdb04ca945ae","unresolved":false,"context_lines":[{"line_number":46,"context_line":"HTTP defines a set of standard response codes on requests, they are"},{"line_number":47,"context_line":"largely grouped as follows:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"* 1xx: compatibility with older HTTP, typically of no concern"},{"line_number":50,"context_line":"* 2xx: success"},{"line_number":51,"context_line":"* 3xx: redirection (the resource is at another location, or is"},{"line_number":52,"context_line":"  unchanged since last requested)"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_40057f43","line":49,"in_reply_to":"fa32b979_6c3eae8c","updated":"2015-06-24 19:52:02.000000000","message":"I think you\u0027re right, but the section seems to suggest this a generic description of HTTP response code.\n\nAnyway, that\u0027s enough bikeshedding for this patch. I really don\u0027t think it makes any difference what we write for 1xx response codes.","commit_id":"ea36338c481e87d1c29ff6498fa606339eb2a2f2"}]}