Skip to content
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

proxy.golang.org: let storage.googleapis.com/proxy-golang-org-prod return responses with 'Access-Control-Allow-Origin: *' #45248

Open
hajimehoshi opened this issue Mar 26, 2021 · 2 comments

Comments

@hajimehoshi
Copy link
Member

@hajimehoshi hajimehoshi commented Mar 26, 2021

Apparently https://proxy.golang.org/ now returns responses with Access-Control-Allow-Origin: *, which is awesome. However, the storage server (https://storage.googleapis.com/proxy-golang-org-prod/...) for zip files does not.

I'd be happy if the storage server could return responses with Access-Control-Allow-Origin: *, so that we could create our own playground where Go tool chain works on browsers completely. Actually, I have succeeded to create a Go toolchain compiled in Wasm (https://github.com/hajimehoshi/asobiba, https://soko.hajimehoshi.com/asobiba/) and now I'm now using a third party's GOPROXY instead.

@seankhliao seankhliao changed the title cmd/go: request: let storage.googleapis.com/proxy-golang-org-prod return responses with 'Access-Control-Allow-Origin: *' proxy.golang.org: let storage.googleapis.com/proxy-golang-org-prod return responses with 'Access-Control-Allow-Origin: *' Mar 26, 2021
@heschi
Copy link
Contributor

@heschi heschi commented Mar 30, 2021

@cagedmantis cagedmantis added this to the Backlog milestone Mar 31, 2021
@katiehockman
Copy link
Member

@katiehockman katiehockman commented Apr 6, 2021

@hajimehoshi we'll take a look at this. Thanks for filing the issue.

@katiehockman katiehockman self-assigned this Apr 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants