fsspec / fsspec/filesystem_spec

get paremeters in HTTPFileSystem

Open
#715 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.4k
Forks
490
Avg merge
2d 3h
Merged PRs (30d)
38

Description

First of all, thanks for your great work. I have been uning FSSpec for a while and it is a great piece of software.

I had a question regarding the HTTPFileSystem. According to https://filesystem-spec.readthedocs.io/en/latest/api.html#fsspec.implementations.http.HTTPFileSystem, extra parameters may be passed to client_kwargs in order to get things as authentication. Well, I do need authentication, but in my case, the authentication is obtained by adding a token as a parameter in the GET requests. For example, if the file is:

http://some-host.com/file.zip

the access to the file is done by using

http://some-host.com/file.zip&token=somehexadecimalvalues

At the moment the only alternafive I figure out is to append the token to the URL manually, but I would like to know if there is a better alternative.

Thanks in advance

Luis

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the HTTPFileSystem entry point and inspect how client_kwargs and GET requests are handled. Determine how query parameters such as an authentication token could be passed without manually changing the URL; done should include a supported way to add those parameters to requests.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
networking
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.