This repository has been archived by the owner on Dec 27, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
CORS issue? #2
Comments
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. |
Shouldn't be too hard to add the headers to Hashbase, I think. |
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. |
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? |
We'll add it to the official instance |
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.
@RangerMauve or anybody else hit a CORS issue using this? Trying to reach hashbase.io using this pinning service, hit this wall right away:
beakerbrowser/hashbase#118
The text was updated successfully, but these errors were encountered: