-
Notifications
You must be signed in to change notification settings - Fork 505
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.
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
Proxying sumdb behind a proxy or upstream #1468
Comments
@wayjam if Athens is proxying to a sum DB, would you want it to cache results locally? |
@arschles I think just a reverse proxy or a middleware with cache are both fine. And if athens can provide two options ideally. |
@wayjam I see. That sounds like it could work! We would never have to expire the cache either, which makes this a lot easier. Would you like to prototype this? No pressure at all if you don't. Just let me know |
@arschles Does it mean the Athens could not utilize
Just ran the server with the config.dev.toml and the envs below: "ATHENS_LOG_LEVEL":"trace",
"ATHENS_DOWNLOAD_MODE":"async_redirect",
"ATHENS_DOWNLOAD_URL":"https://goproxy.cn",
"ATHENS_SUM_DBS":"https://sum.golang.org",
"ATHENS_GO_BINARY_ENV_VARS":"GOPROXY=https://goproxy.cn,direct; GOSUMDB=sum.golang.google.cn", Got the error messages on the client side when I ran
|
Describe the solution you'd like
Now
SumDBs
will proxy sumdb direct to the accually sumdb server insteads of behine the value ofGlobalEndpoint
Describe alternatives you've considered
What 's the best way to describe?
SumDB
matchhttps://(?<proxyHost>.*)/sumdb/(?<sumdb id>.*)
, use idsumdb id
upstream/sumdb/id
The text was updated successfully, but these errors were encountered: