hydrusnetwork / hydrusnetwork/hydrus
Client API request proxy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.2k
- Forks
- 207
- PR merge metrics
- No merged PRs in 30d
Description
The idea here is to provide an api endpoint to be able to make arbitrary http requests (GET and POST preferably) that will be executed through Hydrus and be able to use the cookies and headers set up in the client for whatever domain.
One use of this for me would be saucenao lookups in Hydrus Web. Since saucenao doesn't have CORS headers Hydrus Web can't directly access their API so the idea would be to put your saucenao api key in the headers settings in Hydrus and then Hydrus Web could make requests to saucenao through the Hydrus API which would bypass the need for CORS and automatically have the right header.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or existing entry points. Start by locating Hydrus's API endpoint registration and the client cookie and header settings, then establish the supported GET/POST request behavior, domain restrictions, and authentication requirements; done means documented, tested proxy requests that safely use the configured client state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100