-
Notifications
You must be signed in to change notification settings - Fork 49
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
[Bug] SPARQL access to queryid header leads failed search #393
Comments
I am trying to have a look at the code to see if I can suggest a patch. |
Possibly related |
@JervenBolleman Can you try using Graph Explorer with the proxy server? You can refer to the notes in this comment for some basic instructions: |
ok, I was able to get https://beta.sparql.swisslipids.org/ working locally with the proxy server. It did require some code changes around how the proxy server is constructing the request. The big one was adding the |
@JervenBolleman Can you try my branch and configuration settings to see if it works for you? |
I'm sorry, I closed this prematurely. |
@kmcginnes thank you. This works nicely with the proxy. I am still going to make this work without the proxy out of the box by adding the expected required headers to our endpoints. |
Description
Attempting to run graph-explorer on a sparql endpoint specifically https://beta.sparql.swisslipids.org fails in firefox due to an
queryid
is not a standard header and the code should expect that no access is possible.Environment
Steps to Reproduce
Add a database https://beta.sparql.swisslipds.org sync, and then open the explorer for the dataset
/explorer/#/graph-explorer
search for "15-methylhexadecasphinganine" see failure message red box and CORS failures in the firefox console.
Expected Behavior
A successful search
Important
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
The queryid is an interesting header to add, so I will add this to our endpoints and reproducing this in the future might be hard.
I am trying to have a look at the code to see if I can suggest a patch.
The text was updated successfully, but these errors were encountered: