[jira] [Comment Edited] (JENA-652) Fuseki SPARQL update endpoint does not set CORS headers on an OPTIONS request

["Andy Seaborne (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JENA-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13936254#comment-13936254 ] 

Andy Seaborne edited comment on JENA-652 at 3/15/14 5:45 PM:
-------------------------------------------------------------

Commit 1577904 from [~andy.seaborne] in branch 'jena/trunk'
[ https://svn.apache.org/r1577904 ]

Better temporary fix for JENA-652.
If the filter expressions are completely handled by both (union) branches, 
then optimization is safe.
----
This fix is cautious in that it tries to place the filters inside the union branch but only if all the expressions of the filter are pushed into both branches.  Breaking up the expression list is possible to consider each expession one-by-one, so is pushing in a filter expression and if it goes into one branch but not the other, leaving a modified branch with the and also keeping it to be placed elsewhere.  Applying a filter twice is safe, filters are relatively cheap (caution about EXISTS) and a good placement can be very effective.


was (Author: jira-bot):
Commit 1577904 from [~andy.seaborne] in branch 'jena/trunk'
[ https://svn.apache.org/r1577904 ]

Better temporary fix for JENA-652.
If the filter expressions are completely handled by both (union) branches, 
then optimization is safe.

> 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ä
>            Priority: Minor
>
> 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.2#6252)