Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Response Content-Type vs actual content type #837
This is the behaviour that I observe with a GET on the ID of a STU3 resource, e.g. http://fhirtest.uhn.ca/baseDstu3/Medication/247168:
Considering that the resource I am requesting is a STU3 resource, why does it respond with
I think it's probably OK to be tolerant of all the combinations, but why not call the response what it is:
This pattern of responses is kind of a careful balance between complying to the FHIR spec, and being tolerant of clients that aren't fully compliant (i.e. postel's law).
Are any of these causing issues for you? If this logic is causing problems I'm certainly happy to try and address them..
I suppose this one would probably be the best candidate for changing, since the client isn't explicitly requesting the legacy mimetype.
added a commit
Jan 26, 2018
Thanks for the explanation, I can understand returning the old MIME type to clients that have requested it, some of whom may be intolerant of receiving anything else.
I think the two that could be improved are 4 and 5. These currently return the old MIME type, even though the client has not requested it.
I think there is a case for changing these to return a