[
https://issues.apache.org/jira/browse/STANBOL-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184450#comment-14184450
]
Cristian Petroaca commented on STANBOL-1335:
--------------------------------------------
A few questions:
1. Is it necessary to create a configuration for the CorsFilter where the user
can specify the allowed origins, allowed methods, etc? Or is it enough if I
assume allowed Origins = * and allowed Methods = all, etc?
2. It seems that the QueryHeadersFilter you gave as example relies on the
presence of some cors headers? Should I take into account that my filter needs
to be executed before the Query... one?
3. I got most of the cors code (as in 95%) from here
http://grepcode.com/file/repo1.maven.org/maven2/org.apache.tomcat/tomcat-catalina/7.0.42/org/apache/catalina/filters/CorsFilter.java.
Since Tomcat is also an Apache project I assume there is no legal issue with
using the same logic?
> Re-enable CORS support
> ----------------------
>
> Key: STANBOL-1335
> URL: https://issues.apache.org/jira/browse/STANBOL-1335
> Project: Stanbol
> Issue Type: Sub-task
> Reporter: Rupert Westenthaler
> Fix For: 1.0.0
>
>
> The Stanbol trunk currently does not support CORS as the old code used in
> 0.12 is deactivated and the proposed solution - by using a Servlet Filter -
> was not yet implemented.
> Workaround: Use the 0.12.0 release or the 0.12-releasing branch version
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
