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
Expected behavior
nifti-volume-loader can be configured when registering it (e.g. in a beforeSend method similar to dicomImageLoader), allowing for custom headers, e.g., for authentication towards the server.
Why should we prioritize this feature?
Without this feature it is impossible to use the nifti-volume-loader in our project, because we require authentication towards a server that contains the nifti files. This will be the case for a lot of production applications with proper data security measures, especially in the medical domain and its patient privacy concerns.
The text was updated successfully, but these errors were encountered:
nagychris
changed the title
[Feature Request]
[Feature Request] nifti-volume-loader should be configurable to include custom (auth) headers in requests (beforeSend)
Dec 9, 2024
What feature or change would you like to see made?
Current behavior
When using https://github.com/cornerstonejs/cornerstone3D/tree/main/packages/nifti-volume-loader, it is currently not possible to configure any headers for the requests to retrieve the nifti volumes.
Expected behavior
nifti-volume-loader can be configured when registering it (e.g. in a
beforeSend
method similar to dicomImageLoader), allowing for custom headers, e.g., for authentication towards the server.Why should we prioritize this feature?
Without this feature it is impossible to use the nifti-volume-loader in our project, because we require authentication towards a server that contains the nifti files. This will be the case for a lot of production applications with proper data security measures, especially in the medical domain and its patient privacy concerns.
The text was updated successfully, but these errors were encountered: