[Feature Request] Cloud Sync: add control over Authorization forwarding on redirects for self-hosted WebDAV
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
I run OpenList on a low-resource cloud server with OneDrive mounted as the backend.
To avoid the server becoming a bandwidth/storage bottleneck, downloads are served via 302 redirect to the upstream storage URL instead of being proxied entirely by the server. RetroArch's current redirect handling forwards Authorization to the redirected target, which can cause the request to fail with InvalidArgument.
Maybe add a switch for Authorization forwarding on redirects to be controlled explicitly for self-hosted WebDAV.
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
No file or test is named. Start by locating RetroArch’s HTTP redirect handling and the self-hosted WebDAV or cloud-sync path; trace how 302 responses handle Authorization, then define and verify the switch’s enabled and disabled behavior without forwarding credentials unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100