-
Notifications
You must be signed in to change notification settings - Fork 27
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
Fetching submission context from cloudflare fails #53
Comments
I'm pretty sure all DIF specs are published via GitPages, and I'm not sure how we would publish |
It fails on preload into cache. Workaround would be to hard code the context into cache, but i think a context should still be resolvable in any case.
|
On my machine:
|
At any rate, I am not DIF tech support, I can't help resolve GitHub Pages hosting, or DIF Cloudflare account related issues. |
True that. This is why i'm a big fan of ld context on IPFS ;) |
Haha, of course not, Orie, was just wondering if you had guidance on the resolvability requirements and/or preloading of such things. I noticed the context in question had been uploaded by one of your commits. curling from here in Germany gets me a response that looks just like Orie's (i.e., 301), not like OP's, although in a browser the same URL returns: Maybe as a quick fix I could just upload this particular document to public IPFS for you? :D |
Maybe DIF should tack on an IPNS verificationMethod to its did:web... 💃 |
Nice Idea :D i already did and replaced the URL with ipfs://QmRSE16DGVRzNdzEeoA14nsG9iLZzHUz9sbYPqaZncCEJ1 Works/verifies like a charm now :) |
As mentioned above, we are about to switch towards referencing contexts via IPFS mostly as this mitigates any issues with versioning, availability and integrity |
I made a small PR to the (i guess) most used JSON-LD library by digitalbazaar, for those interested in the topic :) |
This is a DIF-wide issue; need to determine where to track.
|
TODO: someone with permissions move this to spec-up repo |
When fetching your presentation_submission context ( https://identity.foundation/presentation-exchange/submission/v1 ) from our server, the request fails, as it gets stuck in the cloudflare bot filter.
Could you consider not hosting the context on cloudflare, but on a more machine accessible location?
The text was updated successfully, but these errors were encountered: