Stream: implementers
Topic: Etag as conditional for read interaction
Florian Apolloner (Mar 26 2019 at 13:11):
Hi,
the STU3 as well as R4 docs list the ETag as optional conditional for the read interaction (http://hl7.org/fhir/http.html#summary). What does this mean? I have never seen http requests carry over an ETag, should this say If-Match instead?
Thanks,
Florian
Lloyd McKenzie (Mar 26 2019 at 15:02):
I think this is intended to reflect that ETag is optional in the read response. If so, differentiating which headers are for request vs. response would be useful. @Ewout Kramer @Grahame Grieve ?
Grahame Grieve (Mar 26 2019 at 20:52):
I think it's the response, yes
Lloyd McKenzie (Mar 26 2019 at 21:01):
@Florian Apolloner Can you submit a change request for us to clarify in the table which are headers for the request vs. response?
Brian Postlethwaite (Mar 26 2019 at 23:07):
I have a full table explaining all headers that could go into R5.
Florian Apolloner (Mar 27 2019 at 07:30):
@Lloyd McKenzie Yeah, that makes more sense; we should also add the LastModified header then. Sorry for the stupid question, but where would I submit a change request?
Lloyd McKenzie (Mar 27 2019 at 14:39):
Not a stupid question :). At the bottom of every page in the spec is a "propose a change" link. There's a 1-time registration process and a manual review where we check that you seem like a real human and then you'll be set to propose away.
Last updated: Apr 12 2022 at 19:14 UTC
