include access token in client requests, if defined #133
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this allows h5web to work in CORS jupyterlab deployments and JupyterHub 4.1 which has stricter XSRF rules
|
I just encounter this yesterday and was about to look into it, thanks for the PR! |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows h5web to work in a cross-site jupyterlab deployments (where backend and static pages are on different domains) and JupyterHub 4.1, which has stricter XSRF rules, and matches JupyterLab's own API requests made with ServerConnection.
Viewing hdf5 files results in a 403 error in these two scenarios without this patch.