-
Notifications
You must be signed in to change notification settings - Fork 2
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
identify the shapes for which to develop ShEX #67
Comments
Okay, done:
But now I'm stuck (cc @andrawaag @nunogit): I think we first need HTTPS support on http://sparql.wikipathways.org/ first. |
Yeah, the HTTPS miltia has seized control of the browsers. You're basically stuck setting up HTTPS everywhere in order to work in today's Web. |
HTTP is working now. |
Meaning the browser is is no longer refusing to load HTTP resources? Is it because the rawgit image you loaded was from HTTP instead of HTTPS? |
Interesting questions. Not sure. I always thought it was the HTTP/-S difference between the currently loaded HTML and the additional remote resources that mattered, not just between the additional remote resources. Anyway, the one thing that changed is that the WikiPathways SPARQL endpoint now supports HTTPS too. I also note the typo in my comment of two days ago, which should have said: "HTTPS is working now" :) |
Ahh yes, that implies a different subject. Re HTTP/S. This is a continuously-shifting battle-ground. As last I understood it, most browsers would refuse to fetch HTTPS from a page loaded with HTTP. At some point after that change, I believe rawgit changed to only serve HTTPS, which had the effect of requiring that all required resources be available by HTTPS. Then the squirrels arrived and chewed off my fingers and I swore off web development forever. |
Some initial info here: https://github.com/egonw/shexWorkingBio/blob/master/index.md |
The list (growing):
The text was updated successfully, but these errors were encountered: