Post by david on May 21, 2024 4:12:11 GMT
Looking at the Certificate resource, for example.
The CertificateString and CertificateType properties are required-on-create, so
they should be passed in a POST request, understandable.
But what about the other properties? Could the SerialNumber property
be accepted as part of the POST request? It is marked as read-only,
does that mean it should not be accepted as part of the POST request,
and rather it is created by the service?
The Id property is also marked as read only, yet the
specification says this:
So that makes it should like Id, as well as any other property, could be accepted on POST to create a resource, but the unused ones will be ignored?
How would a client know which properties will be ignored and which wouldn't?
Having a hard time trying to wrap my head around this. Thank you.
The CertificateString and CertificateType properties are required-on-create, so
they should be passed in a POST request, understandable.
But what about the other properties? Could the SerialNumber property
be accepted as part of the POST request? It is marked as read-only,
does that mean it should not be accepted as part of the POST request,
and rather it is created by the service?
The Id property is also marked as read only, yet the
specification says this:
The service may ignore any service-controlled properties, such as Id, which would force the service to overwrite those properties. Additionally, the service shall set the Location header in the response to the URI of the new resource.
So that makes it should like Id, as well as any other property, could be accepted on POST to create a resource, but the unused ones will be ignored?
How would a client know which properties will be ignored and which wouldn't?
Having a hard time trying to wrap my head around this. Thank you.
