[JENA-2283] Allow setting the SPARQL endpoint.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Jena 4.4.0
• Fix Version/s: Jena 4.5.0
• Component/s: Fuseki UI
• Assignee: Bruno P. Kinoshita
• Reporter: Andy Seaborne
• Created: 16/Feb/22 10:22
• Updated: 04/May/22 21:21
• Resolved: 19/Feb/22 19:22

Description

The old UI had a "SPARQL endpoint" box.

That would be useful for plugging the UI into any SPARQL endpoint without relying on introspection of the server.

As reported: https://stackoverflow.com/questions/71111989/fuseki-4-4-ui-set-endpoint-for-update-queries, it is also a "trick" for setting the endpoint to the update service and sending SPARQL Update.

The old API sets the HTML form parameter correctly - probably yasgui knows whether it is a query string or an update string and sets the HTML form parameter correctly (query= or update=) for application/x-www-form-urlencoded.

---

In Fuseki, if a request goes to a named service ("/dataset/query", "/dataset/update") the service will execute it without being too worried about the content -type. Sending to "/dataset" does require a content type or correct HTML form parameter.

curl -XPOST -H 'Content-type: ' --data 'INSERTDATA { <x:s> <x:p> <x:o>}' http://localhost:3030/ds/update

works - the -H 'Content-type: ' turns off curl adding application/x-www-form-urlencoded.

Issue Links

• links to: GitHub Pull Request #1200