Describe the bug
Our FHIR server is customized to require an additional request header for every request. When using client.request() we can do something like below:
The FhirClient would GET the AllergyIntolerance record with the custom request header, it then follow-up with another GET to retrieve the referenced Patient record. However, the follow-up reference GET does not pass in the custom request header.
Expected behavior
Please propagate the request headers when performing additional fetch when resolving references.
Client-side (please complete the following information):
OS: Windows
Browser: Chrome
Version 126.0.6478.127 (Official Build) (64-bit)
Front-end Framework(s): React
Server-side (please complete the following information):
Not relevant.
Describe the bug Our FHIR server is customized to require an additional request header for every request. When using
client.request()
we can do something like below:The initial call would be fine, however the subsequent call to resolve the references does not propagate the header.
To Reproduce For example, I have an AllergyIntolerance record in my FHIR server which references to a Patient resource.
The FhirClient would GET the
AllergyIntolerance
record with the custom request header, it then follow-up with another GET to retrieve the referencedPatient
record. However, the follow-up reference GET does not pass in the custom request header.Expected behavior Please propagate the request headers when performing additional fetch when resolving references.
Client-side (please complete the following information):
Server-side (please complete the following information): Not relevant.
Additional context N/A