Open umakaadmin opened 8 years ago
Actually your accept header is wrong.
application/sparql-results+json, application/sparql-results+xml, text/boolean, text/tab-separated-values;p=0.8, text/csv;p=0.2, */*;p=0.1
should be
application/sparql-results+json, application/sparql-results+xml, text/boolean, text/tab-separated-values;q=0.8, text/csv;q=0.2, */*;q=0.1
q
as in quality
@JervenBolleman
Thank you for your report.
The first problem comes from the judgement of liveness.
If UmakaData judges the endpoint NOT alive, it does not investigate the endpoint further.
So, CORS = false
is not accurate, we should indicate CORS = NOT CHECKED
.
I'm sorry for confusing you.
I assume that UniProt endpoint supports content negotiation, but UmakaData seems to fail to obtain the result as sparql-results+json
or application/sparql-results+xml
.
We are investigating about that.
The second problem seems to be same as egonw mentioned on #101. This will be solved in few days.
Thanks!
@dsatoh the content negotation failure is due to the p instead of q on your side. Leading our endpoint to understand none of the accept header contents and sending back HTML.
@JervenBolleman Thank you for your feedback. We updated the sparql-client gem to the newer version, and now we can get correct response as application/sparql-results+json
from UniProt endpoint. This update will have the effect from the next crawling(will be run on Jun 14th 00:00:00 UTC).
The UniProt endpoint has CORS enabled, VOID and service description and supports the formats. Something strange is going on with your request. Can you tell us some details about how exactly you are asking for results?