Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[components] Handle authentication in fetch #25

Open
severo opened this issue Nov 7, 2024 · 3 comments
Open

[components] Handle authentication in fetch #25

severo opened this issue Nov 7, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@severo
Copy link
Contributor

severo commented Nov 7, 2024

See https://github.com/severo/hyparam--space/blob/db6d39b316c98b4ad0c1820afe1abe1f198be688/src/contexts/authContext.ts for example
@severo severo mentioned this issue Nov 7, 2024
Merged
@severo
Copy link
Contributor Author

severo commented Nov 8, 2024

see hyparam/hyparquet#34

@severo severo added the enhancement New feature or request label Nov 21, 2024
@severo
Copy link
Contributor Author

severo commented Nov 21, 2024 •
edited
Loading

Note that passing authentication might be easier if we don't rely on an inlined worker (see #15, and #26), if the authentication goes through a cookie

@severo
Copy link
Contributor Author

severo commented Nov 22, 2024

I think the requestInit parameter should be passed inside ParsedKey. We could add options to parseKey, to add a preconfigured token in case it's an URL from some site (HF for example).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@severo