[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CAMP-41) HTTP PUT and read-only/immutable attributes
[ http://tools.oasis-open.org/issues/browse/CAMP-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32142#action_32142 ] Anish Karmarkar commented on CAMP-41: ------------------------------------- This is a dup of https://tools.oasis-open.org/issues/browse/CAMP-34 > HTTP PUT and read-only/immutable attributes > ------------------------------------------- > > Key: CAMP-41 > URL: http://tools.oasis-open.org/issues/browse/CAMP-41 > Project: OASIS Cloud Application Management for Platforms (CAMP) TC > Issue Type: Bug > Components: Spec > Reporter: Anish Karmarkar > Assignee: Anish Karmarkar > > 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? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]