|
Post by JenHuang on Sept 26, 2019 11:39:29 GMT
As I checked the redfish specification and there is not clearly definition for HTTP POST request body if the property is null, but clearly define the null property value is legal for HTTP PATCH.
HTTP POST is different with PATCH, the purpose for POST request is going to create resource or action. In the cases, null property value doesn't have clear purpose like PATCH. Should redfish server block the null property value for HTTP POST request?
|
|
|
Post by mraineri on Oct 1, 2019 18:17:37 GMT
You are correct; null for a property should be blocked by a Redfish Service in a POST request. If the client doesn't have a value for a property in a new resource, I would expect the property to not even be part of the request body. We'll need to add this to the spec for clarity.
|
|