Stream: implementers
Topic: empty POST bodies
Josh Mandel (Oct 16 2017 at 20:11):
On the FHIR Infrastructure workgroup call, we just discussed GF#13632, which asks how to POST to an operation that requires no parameters. We think an empty request body is the right way to express this, but we wanted to check here, with server developers, about whether omitting the Content-type header on the request would cause any challenges.
@Grahame Grieve @James Agnew @Ewout Kramer @nicola (RIO/SS) @Richard Ettema and other server devs: any issues accepting a request like the following (with no body, no Content-type header, and a specified Accept header)?
POST /DocumentReference/Composition/123/$generate Content-length: 0 Accept: application/fhir+json
nicola (RIO/SS) (Oct 16 2017 at 20:26):
No problem to support such type of operations.
Grahame Grieve (Oct 16 2017 at 20:42):
it would certainly require me to make some changes to my server, but any solution other than requiring an irrelevant parameter would, so I'm fine with it
Ewout Kramer (Oct 16 2017 at 20:52):
@Christiaan Knaap ?
Richard Ettema (Oct 16 2017 at 22:49):
No problem from my perspective. No request body means no request Content-Type header and vice versus.
Christiaan Knaap (Oct 17 2017 at 06:32):
No problem, we don't consider the Content-Type until an operation actually tries to read the body.
James Agnew (Oct 17 2017 at 21:03):
Yup, no conerns here.
Brian Postlethwaite (Nov 10 2017 at 11:23):
Changes will be needed on my server, but seems reasonable
Last updated: Apr 12 2022 at 19:14 UTC
