You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@stanbol.apache.org by "Cristian Petroaca (JIRA)" <ji...@apache.org> on 2014/10/27 16:57:34 UTC

[jira] [Comment Edited] (STANBOL-1335) Re-enable CORS support

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

Cristian Petroaca edited comment on STANBOL-1335 at 10/27/14 3:57 PM:
----------------------------------------------------------------------

On no 2 : I guess what I am trying to figure out is whether the QueryHeadersFilter needs in any circumstances to have the CORS specific headers in the ServletResponse before it executes?


was (Author: cpetroaca):
On no 2 : I guess what I am trying to figure out is whether the QueryHeadersFilter needs to have the CORS specific headers in the ServletResponse before it executes?

> 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)