Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-1463

Align wording on "safe" and "idempotent" with RFC 7231

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: V4.0_CS01
    • Fix Version/s: V4.0_CSD02
    • Component/s: Repeatable Requests
    • Labels:
      None
    • Environment:

      Proposed

    • Proposal:
      Hide

      In 2 Repeatable Requests change

      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.

      In 10.2 Client Conformance change

      If a client wants to safely repeat a request, a client:

      1. MUST specify the Repeatability-Request-ID header in an unsafe request (section 3.1.1)
      2. MUST specify the Repeatability-First-Sent header in a an unsafe request (section 3.1.2)
      Show
      In  2 Repeatable Requests change 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. In 10.2 Client Conformance change If a client wants to safely repeat a request, a client: MUST specify the  Repeatability-Request-ID  header in an unsafe request (section  3.1.1 ) MUST specify the  Repeatability-First-Sent  header in a an unsafe request (section  3.1.2 )

      Description

      Align text with RFC 7231, Section 4.2.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              handl Ralf Handl
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: