[
https://issues.apache.org/jira/browse/STANBOL-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216290#comment-14216290
]
Reto Gmür commented on STANBOL-1335:
------------------------------------
I tend to disagree with Rupert, one doesn't need CORS if the JS is running on
the same server and one needs "Origins = *" to allow scripts from anywhere to
access the features. But it doesn't seem an uncommon usecase to just want to
allow scripts on www.example.com to access the functionality of
stanbol.example.com.
I agree that the feature is easily added, either now or later.
> 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
> Assignee: Reto Gmür
> Fix For: 1.0.0
>
> Attachments: cors_filter.patch
>
>
> 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)
