-
Notifications
You must be signed in to change notification settings - Fork 14
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
4store doesn't seem to be getting the required http headers for update #36
Comments
this is a tcpdump showing the headers are content-type: text/plain. How can I change this?
|
###update okay so I've managed to change the content-type header and I'm still getting a 500 error, but I can't figure out why - here is a tcpdump of a successful curl
and here is an unsuccessful save using same code as above with a modified gem to set the content-type correctly
this gives me a 500 error from 4store as shown below
|
I got some updates working. Had to prefix the saves with 'update=' however I was still getting errors because subqueries aren't supported by 4store which leads me to believe this gem doesn't support 4store. |
Hi - at Swirrl, we haven't tried it with 4store. I'll leave it to some of my more knowledgeable colleagues to reply in more detail, but Tripod relies on the database having a reasonably full and accurate implementation of the SPARQL 1.1 spec. If 4store doesn't do subqueries that is likely to be a problem. |
Thanks for the reply, it may just be a matter of getting the headers and encoding + form prefixes right, even though the error on 4store side said something about not supporting subqueries, 4store claims to be sparql 1.1 compliant which means they do have subqueries, I think? |
the error -
Tripod::Errors::BadSparqlRequest: 400 4store only implements application/x-www-form-urlencoded
This is a 4store SPARQL server v1.1.5
I'm assuming this is because the correct headers are not being used to query 4stores endpoint. Is this supported? If so how can I set the correct headers?
The text was updated successfully, but these errors were encountered: