Andy Seaborne created JENA-2283:
-----------------------------------
Summary: Allow setting the SPARQL endpoint.
Key: JENA-2283
URL: https://issues.apache.org/jira/browse/JENA-2283
Project: Apache Jena
Issue Type: Bug
Components: Fuseki UI
Affects Versions: Jena 4.4.0
Reporter: Andy Seaborne
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.
{noformat}
curl -XPOST -H 'Content-type: ' --data 'INSERTDATA { <x:s> <x:p> <x:o>}'
http://localhost:3030/ds/update
{noformat}
works - the {{-H 'Content-type: '}} turns off curl adding
{{application/x-www-form-urlencoded}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
