You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/pages/Conformance.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,8 @@ The IBM FHIR Server supports a custom header, `X-FHIR-UPDATE-IF-MODIFIED`, for c
58
58
The IBM FHIR Server also supports conditional create-on-update using the `If-None-Match` header. This IBM FHIR Server-specific feature allows clients to use a `PUT` (update) interaction which behaves as follows:
59
59
60
60
1. `If-None-Match: "*"`: If the resource does not yet exist, create the resource and return `201 Created`;
61
-
2. `If-None-Match: "*"`: If the resource does exist, do nothing and return `304 Not Modified`.
61
+
2. `If-None-Match: "*"`: If the resource does exist, do nothing and return `412 Precondition Failed` (default behavior);
62
+
3. `If-None-Match: "*"`: If the resource does exist and the fhir-server-config element `fhirServer/core/ifNoneMatchReturnsNotModified` is set to `true`, do nothing and return `304 Not Modified`.
62
63
63
64
The only supported value for If-None-Match conditional create-on-update is `"*"`. This feature can also be used for `PUT` requests in transaction or batch bundles by specifying the `ifNoneMatch` field similarly in the request element:
64
65
```
@@ -88,7 +89,9 @@ The only supported value for If-None-Match conditional create-on-update is `"*"`
88
89
89
90
```
90
91
91
-
If a match is found, the response bundle entry contains the location of the current resource and a status of `304` (Not Modified):
92
+
If a match is found and the fhir-server-config element `fhirServer/core/ifNoneMatchReturnsNotModified` is not configured or is set to `false`, the condition is treated as an error which will cause transaction bundles to fail, returning a status of `400` (Bad Request). For batch bundles, the entry response status will be `412` (Precondition Failed).
93
+
94
+
If a match is found and the fhir-server-config element `fhirServer/core/ifNoneMatchReturnsNotModified` is set to `true`, the response bundle entry contains the location of the current resource and a response status of `304` (Not Modified):
Copy file name to clipboardExpand all lines: docs/src/pages/guides/FHIRServerUsersGuide.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2048,6 +2048,7 @@ This section contains reference information about each of the configuration prop
2048
2048
|`fhirServer/core/defaultPageSize`|integer|Sets the page size for search and history request results when no `_count` parameter is specified.|
2049
2049
|`fhirServer/core/maxPageSize`|integer|Sets the maximum page size for search and history request results. If a user-specified `_count` parameter value exceeds the maximum page size, then a warning is logged and the maximum page size will be used.|
2050
2050
|`fhirServer/core/maxPageIncludeCount`|integer|Sets the maximum number of 'include' resources allowed per page for search and history request results. If the number of 'include' resources returned for a page of results from a search or history request will exceed the maximum number of 'include' resources allowed per page, then an error will be returned in the request results.|
2051
+
|`fhirServer/core/ifNoneMatchReturnsNotModified`|boolean|When If-None-Match is specified, overrides the standard return status "412 Precondition Failed" to be "304 Not Modified". Useful in transaction bundles for clients not wanting the bundle to fail when a conflict is found.|
2051
2052
|`fhirServer/core/capabilitiesUrl`|string|The URL that is embedded in the default Capabilities statement|
2052
2053
|`fhirServer/core/externalBaseUrl`|string|The base URL that is embedded in the Search bundle response, as of version 4.9.0. Note that the base URL must not include a path segment that matches any FHIR resource type name (case-sensitive). For example, "https://example.com" or "https://example.com/my/patient/api" are fine, but "https://example.com/my/Patient/api" is not.|
2053
2054
|`fhirServer/validation/failFast`|boolean|Indicates whether validation should fail fast on create and update interactions|
@@ -2233,6 +2234,7 @@ This section contains reference information about each of the configuration prop
0 commit comments