[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [odata-comment] aligning "repeatable requests" language with existing specs and question about repeatability for idempotent methods
Hi Erik, Thanks for the feedback, we did not intend to "redefine" RFC 7231. I've opened https://issues.oasis-open.org/browse/ODATA-1463 to track this. Your feedback on the proposed fix would be highly welcome. Thanks in advance Ralf Handl https://www.linkedin.com/in/ralfhandl/ -----Original Message----- From: odata-comment@lists.oasis-open.org <odata-comment@lists.oasis-open.org> On Behalf Of Erik Wilde Sent: Wednesday, 28 July 2021 08:46 To: odata-comment@lists.oasis-open.org Subject: [odata-comment] aligning "repeatable requests" language with existing specs and question about repeatability for idempotent methods hello. https://docs.oasis-open.org/odata/repeatable-requests/v1.0/cs01/repeatable-requests-v1.0-cs01.html#sec_RepeatableRequest says "An unsafe request is a non-idempotent request; that is, a request which has the potential to change the service each time it is executed." this is wording that should be changed. "safe" and "idempotent" requests are defined by HTTP itself, so this shouldn't be redefined by a spec building on HTTP. in HTTP, "an unsafe request is a non-idempotent request" is a false statement, because "safe" and "idempotent" refer to different things: https://datatracker.ietf.org/doc/html/rfc7231#section-4.2 using this definition from RFC 7231, it also isn't quite clear after reading the "repeatable requests" spec why the proposed header fields would have to be used for PUT and DELETE. those methods are defined by HTTP to be idempotent, meaning that requests are repeatable by definition. the "repeatable requests" spec has a more sophisticated model of repeatability, but if these header fields indeed should be used with idempotent HTTP methods, then the spec would need to carefully and clearly talk about how the fundamental repeatability of these methods changes by using the additional header fields. kind regards, dret. -- erik wilde | mailto:erik.wilde@dret.net | | http://dret.net/netdret | | http://twitter.com/dret | -- This publicly archived list offers a means to provide input to the OASIS Open Data Protocol (OData) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: odata-comment-subscribe@lists.oasis-open.org Unsubscribe: odata-comment-unsubscribe@lists.oasis-open.org List help: odata-comment-help@lists.oasis-open.org List archive: http://lists.oasis-open.org/archives/odata-comment/ Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: http://www.oasis-open.org/maillists/guidelines.php Committee: http://www.oasis-open.org/committees/odata Join OASIS: http://www.oasis-open.org/join/
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]