[
https://issues.apache.org/jira/browse/JENA-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181836#comment-14181836
]
Andy Seaborne commented on JENA-652:
------------------------------------
Note that the patch expands on the CORS support already in Fuseki 1.X ("CORS
Allow headers for an OPTIONS")
I have applied the patch to Fuseki 1.X (because it already provided partial
CORS) and the moral equivalent to Fuseki2. But in Fuseki2 CORS support is
disabled for now.
Marked "resolved" so it's clear what's the development codebase but the
discussion about how to enable/disable should continue.
Fuseki2 has a wider range of deployment options so the matter is more
complicated.
> 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)
