[
https://issues.apache.org/jira/browse/JENA-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181206#comment-14181206
]
Osma Suominen commented on JENA-652:
------------------------------------
This has been stuck for a while. I'd like to see a solution, because I'm also
trying to do SPARQL updates from JavaScript (e.g. with SKOSjs) and this is
currently difficult because of the CORS header issue. It requires using some
kind of proxy to make it work.
Either Eetu's patch or using the Cross Origin Filter would be fine.
How would one use the Cross Origin Filter with embedded Jetty? The filter
documentation (linked by Andy above) only mentions setting it up in web.xml,
but as I understand it Fuseki doesn't use web.xml.
> Fuseki SPARQL update endpoint does not set CORS headers on an OPTIONS request
> -----------------------------------------------------------------------------
>
> Key: JENA-652
> URL: https://issues.apache.org/jira/browse/JENA-652
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 1.0.1
> Reporter: Eetu Mäkelä
> Assignee: Andy Seaborne
> Priority: Minor
> Attachments: fuseki-cors.patch
>
>
> Fuseki does not return CORS Allow headers for an OPTIONS request on the
> update endpoint, thus disallowing SPARQL UPDATE requests to be made from
> HTML5 web applications.
> This can probably be fixed just by adding a call to
> {{setCommonHeaders(response);}} into the {{doOptions}} -method of
> {{org.apache.jena.fuseki.servlets.SPARQL_Update}}, identically to how this is
> handled in {{org.apache.jena.fuseki.servlets.SPARQL_Query}} .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
