|
|
Post by jautor on May 20, 2022 18:46:35 GMT
Oh, yes, I didn't look at the specific property name, I was just reading it as a generic array... Mike is correct on that specific property case.
Jeff
|
|
|
|
Post by mharishm on Dec 29, 2022 15:04:25 GMT
Hi
As you pointed out that in spec regarding the empty JSON body in the request for PATCH there is statement something like "Services may accept a PATCH method with an empty JSON object, which indicates that the service should make no changes to the resource."
In one of your comment on "Apr 12, 2022 at 6:46pm" you said technicall we can reject it. Does that mean redfish can reject it with 400 bad request for empty json body in the request?
Also as per the redfish spec statement, as it says "Services may accept", does that mean the implementation can accept the request and return 204 or reject the request by giving 400 bad request (Both are valid).
Because as per ISO/IEC Directives, "may", "need not" refers to "not required".
Please let us know your view on this for us to get more clarity.
Thanks,
Harish M
|
|
|
|
Post by jautor on Dec 30, 2022 21:20:20 GMT
Hi As you pointed out that in spec regarding the empty JSON body in the request for PATCH there is statement something like "Services may accept a PATCH method with an empty JSON object, which indicates that the service should make no changes to the resource." In one of your comment on "Apr 12, 2022 at 6:46pm" you said technicall we can reject it. Does that mean redfish can reject it with 400 bad request for empty json body in the request? Also as per the redfish spec statement, as it says "Services may accept", does that mean the implementation can accept the request and return 204 or reject the request by giving 400 bad request (Both are valid). Because as per ISO/IEC Directives, "may", "need not" refers to "not required". Please let us know your view on this for us to get more clarity. Thanks, Harish M Correct. Both are valid, as you point out, per ISO "may" means "not required". And we try to use "may" when there is no real preference - while "should" typically means we'd prefer that behavior. In this case, as is frequently the case with HTTP handling, the implementation might not have a choice because of processing done at the web server or other software layers outside the control of the Redfish service - and so we don't even want to suggest a preference here because it will absolutely depend on the implementation. Jeff |
|
