You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm cross-posting an issue I've been having with a local install of the Wikidata Query RDF and the Wikidata Query GUI (https://phabricator.wikimedia.org/T308180), which pertains to the GUI being able to access the Blazegraph hosted at http://localhost:9999. I had attempted to follow a solution mentioned here from 2014, but it unfortunately did not work. I absolutely apologize if this is the wrong location to ask, but I'm at a bit of my wit's end, and I hope I'm missing something obvious which you may be able to help me with.
I am curious if there is a recommended option for setting CORS with Blazegraph. In addition to the solution above, I have tried editing the following into every instance of ./WEB-INF/web.xml in the wikidata-query-rdf directory, which also hasn't worked:
Not sure this helps, but I could never get this to work. In the end I used Apache's reverse-proxy mechanism to tunnel any queries. No need for open ports or nginx configuration, and Apache can handle everything CORS-related.
I'm cross-posting an issue I've been having with a local install of the Wikidata Query RDF and the Wikidata Query GUI (https://phabricator.wikimedia.org/T308180), which pertains to the GUI being able to access the Blazegraph hosted at
http://localhost:9999
. I had attempted to follow a solution mentioned here from 2014, but it unfortunately did not work. I absolutely apologize if this is the wrong location to ask, but I'm at a bit of my wit's end, and I hope I'm missing something obvious which you may be able to help me with.I am curious if there is a recommended option for setting CORS with Blazegraph. In addition to the solution above, I have tried editing the following into every instance of
./WEB-INF/web.xml
in thewikidata-query-rdf
directory, which also hasn't worked:Any help would be incredibly appreciated! Thank you for your time!
The text was updated successfully, but these errors were encountered: