microsoft / microsoft/fhir-server
self url is incorrect for bundle results using continuation token
Nobody has claimed this yet.
- Dominant language
- TSQL
- Stars
- 1.4k
- Forks
- 592
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 41
Description
Describe the bug
When requesting a "next" bundle result set with continuation token, the resulting "self" url is not consistent with the expected value.
FHIR Version?
R4
Data provider?
CosmosDB
To Reproduce
Steps to reproduce the behavior:
- Query for a paginated result set, e.g. {{fhir_uri}}/Device?_count=10
- Query for the "next" result set, e.g. {{fhir_uri}}/Device?_count=10&ct=....
Expected behavior
the self uri of the second result set should contain all the parameters, including the ct
Actual behavior
The self uri contains only the original (first) url
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the R4 request flow at the FHIR endpoint with a paginated Device query, then follow how the continuation token is handled when generating the bundle's self URL. Compare the second result set with the original request and verify that the self URL retains every parameter, including ct.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100