Stream: implementers
Topic: REST API: 202 Location/ETag
Alexander Henket (Nov 25 2021 at 15:47):
I'm trying to wrap my head around HTTP 202. There is a very small hint that processing a batch MAY lead to HTTP 202. HTTP 202 is only allowed for delete it seems, hence not create.
So, assuming HTTP 202 is allowed, and knowing that it would mean "The request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, and may be disallowed when processing occurs." -- would it be reasonable to assume that you could be unable to send Location and/or ETag at that point in time because you haven't actually processed the request into anything?
And if yes: can I truly assume my transaction bundle was successfully processed if a 202 comes back? I'm thinking no, because I can only say it was safely committing _for_ processing.
Paul Church (Nov 25 2021 at 15:50):
I believe HTTP 202 applies in the case of respond-async - https://www.hl7.org/fhir/async.html
Given that response I would not expect a location or etag, and the response only means that the request was accepted for processing.
Last updated: Apr 12 2022 at 19:14 UTC
