Uploaded image for project: 'OASIS Cloud Application Management for Platforms (CAMP) TC'
  1. OASIS Cloud Application Management for Platforms (CAMP) TC
  2. CAMP-41

HTTP PUT and read-only/immutable attributes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Spec
    • Labels:
      None
    • Proposal:
      Hide

      Direction for a proposal:

      a) Are clients are allowed to send RO/immutable attributes: YES
      b) Are clients required to send RO/immutable attribute: YES, if they did exist in the last GET.
      c) Can client change immutable attribute in a PUT request: NO (MUST NOT)
      d) if the value of the RO/immutable attribute has been changed by the client the server MUST throw a 4xx error

      To make things unambiguous, remove the attribute constraints 'Mutability' and 'Writable' and instead use new attribute constraints:
      Unchangeable, Server-Changeable, Client-Chanageable (or equivalent)

      Show
      Direction for a proposal: a) Are clients are allowed to send RO/immutable attributes: YES b) Are clients required to send RO/immutable attribute: YES, if they did exist in the last GET. c) Can client change immutable attribute in a PUT request: NO (MUST NOT) d) if the value of the RO/immutable attribute has been changed by the client the server MUST throw a 4xx error To make things unambiguous, remove the attribute constraints 'Mutability' and 'Writable' and instead use new attribute constraints: Unchangeable, Server-Changeable, Client-Chanageable (or equivalent)

      Description

      The spec has a concept of read-only and immutable attributes that cannot be changed by the client.
      HTTP PUT semantics demand that the client send a resource representation that is a full replacement for the existing resource.
      This raises a few questions:
      1) can a client include read-only/immutable attributes in a PUT request?
      2) should the client include read-only/immutable attributes in a PUT request?
      2.a) if not, is that a request to delete the attribute?
      2.b) if yes, should the server check the value to ensure that they are unchanged?
      2.b.i) if server does check the value, what does it do if it is different? ignore, error? what should be the returned status code?

        Attachments

          Activity

            People

            • Assignee:
              akarmark Anish Karmarkar (Inactive)
              Reporter:
              akarmark Anish Karmarkar (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: