From 3c4c6f7925b35c8684748e92317e7a504741815a Mon Sep 17 00:00:00 2001 From: James Agnew Date: Fri, 4 Oct 2019 09:55:14 -0400 Subject: [PATCH] Don't allow Content-Location header to dictate version for updates --- .../BaseOutcomeReturningMethodBinding.java | 24 ++++++------------ .../server/method/UpdateMethodBinding.java | 25 ------------------- src/changes/changes.xml | 6 +++++ 3 files changed, 14 insertions(+), 41 deletions(-) diff --git a/hapi-fhir-server/src/main/java/ca/uhn/fhir/rest/server/method/BaseOutcomeReturningMethodBinding.java b/hapi-fhir-server/src/main/java/ca/uhn/fhir/rest/server/method/BaseOutcomeReturningMethodBinding.java index 5a4e95c5543..e6112605cc9 100644 --- a/hapi-fhir-server/src/main/java/ca/uhn/fhir/rest/server/method/BaseOutcomeReturningMethodBinding.java +++ b/hapi-fhir-server/src/main/java/ca/uhn/fhir/rest/server/method/BaseOutcomeReturningMethodBinding.java @@ -78,9 +78,7 @@ abstract class BaseOutcomeReturningMethodBinding extends BaseMethodBinding allowableRequestTypes = provideAllowableRequestTypes(); @@ -239,14 +241,4 @@ abstract class BaseOutcomeReturningMethodBinding extends BaseMethodBinding + + HTTP PUT (resource update) operations will no longer allow the version to be specified in a + Content-Location header. This behaviour was allowed in DSTU1 and was never removed from HAPI even though + it hasn't been permitted in the spec for a very long time. Hopefully this change will not + impact anyone! +