Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Configure server to override "self" URIs with external path
See original GitHub issueIs your feature request related to a problem? Please describe. We’re running the FHIR Server behind a proxy and that proxy modifies the request URLs.
Request come in to an endpoint like https://[host]/wh-fhir-dev/api/v4 but the server is returning URIs like https://[host]/fhir-server/api/v4/$export-status?job=9.
Is there a way to use the origin request URL in the server URLs returned by the server?
I think it affects at least:
- search result
selfuri - Bundle entry fullUrl values
- bulkimportexport polling URLs
Describe the solution you’d like https://[host]/wh-fhir-dev/api/v4 Either:
- a setting the server will use as the “base” in all self uris; or
- a way to tell the server which HTTP header has the original request URI (so it can use that to construct self uris)
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
but I agree that adding a new config in fhir server side sounds like a simpler solution.
Confirmed with my above test