Skip to content
This repository has been archived by the owner on Dec 27, 2022. It is now read-only.

CORS issue? #2

Open
DougAnderson444 opened this issue Aug 15, 2019 · 6 comments
Open

CORS issue? #2

DougAnderson444 opened this issue Aug 15, 2019 · 6 comments

Comments

@DougAnderson444
Copy link

@RangerMauve or anybody else hit a CORS issue using this? Trying to reach hashbase.io using this pinning service, hit this wall right away:

blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

beakerbrowser/hashbase#118

@RangerMauve
Copy link
Collaborator

Yeah, I think I brought this up with @pfrazee before. You'll need to host your own pinning service that's got the appropriate CORS headers set.

@RangerMauve
Copy link
Collaborator

Shouldn't be too hard to add the headers to Hashbase, I think.

@DougAnderson444
Copy link
Author

I agree. Been chatting with Paul about it, I'm going to try to do some testing to see if there are any issues with cookies and credentials with the cross origin before committing the PR.

@RangerMauve
Copy link
Collaborator

Oh hell yeah. Is it going to make it into the official hashbase service? Or is it just a flag that people can set on their own versions?

@pfrazee
Copy link
Member

pfrazee commented Aug 16, 2019

We'll add it to the official instance

@RangerMauve
Copy link
Collaborator

OMG! That's wonderful! It opens the door for so many possibilities! 😍 I'll double check that dat-store has the proper CORS headers too.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants