fix(123pan): proxy IP-bound downloads#9577
Open
junge128 wants to merge 2 commits into
Open
Conversation
added 2 commits
July 17, 2026 16:32
123Pan now binds download URLs to the IP that requests them. Forwarding the client IP no longer affects that binding, so direct links fail with download error 50001 when AList and the client use different egress IPs.\n\nForce this driver through AList's download proxy and remove the ineffective forwarded-IP headers.
Use errors.New for API-provided login errors so the driver passes the Go printf analyzer without treating provider messages as format strings.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Background
123Pan now binds the final CDN URL to the egress IP that resolves the download link. In a real deployment, the same freshly generated link returned HTTP 200 from the AList host but HTTP 403 with code 1010 and download err: 50001 from a client using a different egress IP.
Passing the client address through X-Forwarded-For, X-Real-IP, or both did not change the result. Proxying the file through AList keeps link resolution and download on the same egress IP and fixes the failure for existing storages regardless of their web_proxy setting.
This intentionally makes 123Pan downloads consume AList server bandwidth.
Testing