Skip to content

fix(rest): parse bundle entry methods through one shared matcher #515

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aacruzgon wants to merge 2 commits into from
Open

fix(rest): parse bundle entry methods through one shared matcher #515

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bf20420
fix(rest): parse bundle entry methods through one shared matcher
aacruzgon Aug 5, 2026
a09bc01
docs(rest): document entry-method matching and the PATCH/HEAD refusals
aacruzgon Aug 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion crates/rest/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -499,6 +499,15 @@ curl -X POST http://localhost:8080/ \
}'
```

### Entry Methods

`Bundle.entry.request.method` is matched **case-sensitively** in both bundle types.
It is a `code` with a required binding to `http://hl7.org/fhir/ValueSet/http-verb`,
whose concepts are `caseSensitive: true` and uppercase in every supported FHIR
version — so a lowercase `"post"` is invalid instance data and is refused with
`400`, not silently accepted. `GET`, `POST`, `PUT` and `DELETE` dispatch; `PATCH`
and `HEAD` are refused as described under Current Limitations.

### Conditional Operations in Bundles

- `ifMatch` — **supported.** ETag for optimistic locking on `PUT` **and `DELETE`**
Expand Down Expand Up @@ -528,7 +537,8 @@ endpoints and **not** for bundle entries; reconciling the two is #511.
The following FHIR transaction features are not yet implemented:
- **Conditional interactions in bundle entries** - `[type]?[criteria]` URLs are refused rather than resolved (#511)
- **Conditional reference resolution** - References like `Patient?identifier=12345` are not resolved
- **PATCH method** - PATCH operations in bundles return 501 Not Implemented
- **PATCH method** - PATCH operations in bundles return 501 Not Implemented, in both `batch` (per entry) and `transaction` (whole bundle). Send the patch to the instance endpoint instead
- **HEAD entries** - refused with 405. `HEAD` is a legal `http-verb` code and is served on the instance-read route, but not inside a Bundle
- **Prefer header** - `return=minimal` and `return=OperationOutcome` not honored
- **Duplicate detection** - Same resource appearing twice in a transaction is not detected

Expand Down
Loading
Loading