[
https://issues.apache.org/jira/browse/STANBOL-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184568#comment-14184568
]
Rupert Westenthaler commented on STANBOL-1335:
----------------------------------------------
ad1: I am not aware that anyone has ever configured anything other as "Origins
= *". So I guess this feature is not really needed. Assuming that you implement
the filter as an OSGI Service it can be anyways added later on
ad2: I am not sure if I understand the question. I used the QueryHeadersFilter
as Example for how to do Servlet FIlters in OSGI. The QueryHeadersFilter is not
directly related to CORS. It was implemented to allow CORS put/post requests
from JavaScript on InternetExplorer, because CORS was not fully supported by IE
ad3. Year that fine. Just make sure that the class level javadoc provides a
link to the orign.
> 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)
