Hi all,
I was wiring some code that trys to make a call to a a SPARQL endpoint service
through a javascript XHR. It fails with:
HTTP ERROR: 415
Problem accessing /dataset/sparql. Reason:
Unsupported: application/x-www-form-urlencoded; charset=UTF-8
So I installed firebug and noticed that when the URL is being fetched with an
XHR call it has the following request header.
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
This header is not present when just going to the same URL via the browser, and
when it is not present it works as you might expect. So, I then installed the
Firefox Modify Headers plugin so I could alter the request header I was sending
through the browser, and sure enough adding that one header causes the HTTP
error you see above.
So, since this is not my code but code I'm working with, altering the XHR call
is a little difficult. My question is: should Fuseki bail out when the
Content-Type header is set as so? I should also note that these XHR calls work
when the endpoint is an older version of Joseki (Joseki, not Fuseki).
Thanks,
Tim
