[
https://issues.apache.org/jira/browse/JENA-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707968#comment-14707968
]
Andy Seaborne commented on JENA-1014:
-------------------------------------
[~colinm] -- caveats noted! Thank you for the update.
If this is added to web.xml, then it is fixed for all practical purposes. It
woudl need unpacking and repacking the jar or war to change.
{{<url-pattern>}} is extremely limited in what it can say, especially with no
negation (e.g. for "not *.html"). Adding earlier filters to catch these cases
and differently direct them gets increasing complicated and fragile so it's not
my ideal way of dealing with it. At least shiro.ini is outside the jar/war file.
> Add CORS support to Fuseki2
> ---------------------------
>
> Key: JENA-1014
> URL: https://issues.apache.org/jira/browse/JENA-1014
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Affects Versions: Fuseki 2.0.0, Fuseki 2.3.0
> Reporter: Andy Seaborne
>
> Needs to:
> 1. Work in standalone mode.
> 2. Work when run as a WAR file.
> Proposal:
> 1. Add CORS filter from Jetty to the standalone server.
> 2. Leave it to the Tomcat setup for running as a WAR file on the basis it's a
> choice of deployment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
