You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Sebastian Germesin (JIRA)" <ji...@apache.org> on 2012/05/16 10:57:02 UTC
[jira] [Created] (STANBOL-616) Wrong CORS Response
Sebastian Germesin created STANBOL-616:
------------------------------------------
Summary: Wrong CORS Response
Key: STANBOL-616
URL: https://issues.apache.org/jira/browse/STANBOL-616
Project: Stanbol
Issue Type: Bug
Components: Entity Hub
Affects Versions: 0.9.0-incubating, 0.10.0-incubating
Reporter: Sebastian Germesin
I just had a look at the CORS support in Stanbol and I have a question to that.
In the CORS specification [1], I read that in a CORS request with a preflight the client sets the request header:
Access-Control-Request-Headers: .... (let's say: origin, content-type, accept)
Access-Control-Request-Method: .... (let's say: POST)
and the server (in this case Stanbol) answers with:
Access-Control-Allow-Headers: ... (let's say: origin, content-type, accept)
Access-Control-Allow-Origin: ... (let's say: *)
Access-Control-Allow-Method: (let's say: GET, POST, OPTIONS)
However, when I perform a query to the Entityhub, e.g., http://dev.iks-project.eu:8081/entityhub/entity/
Stanbol answers correctly with
Access-Control-Allow-Headers: origin, content-type, accept
Access-Control-Allow-Origin: *
BUT:
Access-Control-Request-Method: GET, POST, OPTIONS
instead of
Access-Control-Allow-Method: GET, POST, OPTIONS
Gladly, for the GET and POST requests that somehow works anyways, but for a PUT and DELETE request
that fails again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (STANBOL-616) Wrong CORS Response
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler reassigned STANBOL-616:
-------------------------------------------
Assignee: Rupert Westenthaler
> Wrong CORS Response
> -------------------
>
> Key: STANBOL-616
> URL: https://issues.apache.org/jira/browse/STANBOL-616
> Project: Stanbol
> Issue Type: Bug
> Components: Entity Hub
> Affects Versions: 0.9.0-incubating, 0.10.0-incubating
> Reporter: Sebastian Germesin
> Assignee: Rupert Westenthaler
>
> I just had a look at the CORS support in Stanbol and I have a question to that.
> In the CORS specification [1], I read that in a CORS request with a preflight the client sets the request header:
> Access-Control-Request-Headers: .... (let's say: origin, content-type, accept)
> Access-Control-Request-Method: .... (let's say: POST)
> and the server (in this case Stanbol) answers with:
> Access-Control-Allow-Headers: ... (let's say: origin, content-type, accept)
> Access-Control-Allow-Origin: ... (let's say: *)
> Access-Control-Allow-Method: (let's say: GET, POST, OPTIONS)
> However, when I perform a query to the Entityhub, e.g., http://dev.iks-project.eu:8081/entityhub/entity/
> Stanbol answers correctly with
> Access-Control-Allow-Headers: origin, content-type, accept
> Access-Control-Allow-Origin: *
> BUT:
>
> Access-Control-Request-Method: GET, POST, OPTIONS
> instead of
> Access-Control-Allow-Method: GET, POST, OPTIONS
> Gladly, for the GET and POST requests that somehow works anyways, but for a PUT and DELETE request
> that fails again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (STANBOL-616) Wrong CORS Response
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-616.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 0.10.0-incubating
fixed with #1339130
> Wrong CORS Response
> -------------------
>
> Key: STANBOL-616
> URL: https://issues.apache.org/jira/browse/STANBOL-616
> Project: Stanbol
> Issue Type: Bug
> Components: Entity Hub
> Affects Versions: 0.9.0-incubating, 0.10.0-incubating
> Reporter: Sebastian Germesin
> Assignee: Rupert Westenthaler
> Fix For: 0.10.0-incubating
>
>
> I just had a look at the CORS support in Stanbol and I have a question to that.
> In the CORS specification [1], I read that in a CORS request with a preflight the client sets the request header:
> Access-Control-Request-Headers: .... (let's say: origin, content-type, accept)
> Access-Control-Request-Method: .... (let's say: POST)
> and the server (in this case Stanbol) answers with:
> Access-Control-Allow-Headers: ... (let's say: origin, content-type, accept)
> Access-Control-Allow-Origin: ... (let's say: *)
> Access-Control-Allow-Method: (let's say: GET, POST, OPTIONS)
> However, when I perform a query to the Entityhub, e.g., http://dev.iks-project.eu:8081/entityhub/entity/
> Stanbol answers correctly with
> Access-Control-Allow-Headers: origin, content-type, accept
> Access-Control-Allow-Origin: *
> BUT:
>
> Access-Control-Request-Method: GET, POST, OPTIONS
> instead of
> Access-Control-Allow-Method: GET, POST, OPTIONS
> Gladly, for the GET and POST requests that somehow works anyways, but for a PUT and DELETE request
> that fails again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (STANBOL-616) Wrong CORS Response
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-616.
-----------------------------------------
Resolution: Fixed
added missing 's' in #1339131
> Wrong CORS Response
> -------------------
>
> Key: STANBOL-616
> URL: https://issues.apache.org/jira/browse/STANBOL-616
> Project: Stanbol
> Issue Type: Bug
> Components: Entity Hub
> Affects Versions: 0.9.0-incubating, 0.10.0-incubating
> Reporter: Sebastian Germesin
> Assignee: Rupert Westenthaler
> Fix For: 0.10.0-incubating
>
>
> I just had a look at the CORS support in Stanbol and I have a question to that.
> In the CORS specification [1], I read that in a CORS request with a preflight the client sets the request header:
> Access-Control-Request-Headers: .... (let's say: origin, content-type, accept)
> Access-Control-Request-Method: .... (let's say: POST)
> and the server (in this case Stanbol) answers with:
> Access-Control-Allow-Headers: ... (let's say: origin, content-type, accept)
> Access-Control-Allow-Origin: ... (let's say: *)
> Access-Control-Allow-Method: (let's say: GET, POST, OPTIONS)
> However, when I perform a query to the Entityhub, e.g., http://dev.iks-project.eu:8081/entityhub/entity/
> Stanbol answers correctly with
> Access-Control-Allow-Headers: origin, content-type, accept
> Access-Control-Allow-Origin: *
> BUT:
>
> Access-Control-Request-Method: GET, POST, OPTIONS
> instead of
> Access-Control-Allow-Method: GET, POST, OPTIONS
> Gladly, for the GET and POST requests that somehow works anyways, but for a PUT and DELETE request
> that fails again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (STANBOL-616) Wrong CORS Response
Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler reopened STANBOL-616:
-----------------------------------------
Noticed that the correct header is
Access-Control-Allow-Methods
and not
Access-Control-Allow-Method
as stated in this issue
Same for Access-Control-Request-Method(s)
> Wrong CORS Response
> -------------------
>
> Key: STANBOL-616
> URL: https://issues.apache.org/jira/browse/STANBOL-616
> Project: Stanbol
> Issue Type: Bug
> Components: Entity Hub
> Affects Versions: 0.9.0-incubating, 0.10.0-incubating
> Reporter: Sebastian Germesin
> Assignee: Rupert Westenthaler
> Fix For: 0.10.0-incubating
>
>
> I just had a look at the CORS support in Stanbol and I have a question to that.
> In the CORS specification [1], I read that in a CORS request with a preflight the client sets the request header:
> Access-Control-Request-Headers: .... (let's say: origin, content-type, accept)
> Access-Control-Request-Method: .... (let's say: POST)
> and the server (in this case Stanbol) answers with:
> Access-Control-Allow-Headers: ... (let's say: origin, content-type, accept)
> Access-Control-Allow-Origin: ... (let's say: *)
> Access-Control-Allow-Method: (let's say: GET, POST, OPTIONS)
> However, when I perform a query to the Entityhub, e.g., http://dev.iks-project.eu:8081/entityhub/entity/
> Stanbol answers correctly with
> Access-Control-Allow-Headers: origin, content-type, accept
> Access-Control-Allow-Origin: *
> BUT:
>
> Access-Control-Request-Method: GET, POST, OPTIONS
> instead of
> Access-Control-Allow-Method: GET, POST, OPTIONS
> Gladly, for the GET and POST requests that somehow works anyways, but for a PUT and DELETE request
> that fails again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (STANBOL-616) Wrong CORS Response
Posted by "Suat Gonul (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suat Gonul reopened STANBOL-616:
--------------------------------
Assignee: Suat Gonul (was: Rupert Westenthaler)
Extra "s" at the end of "Access-Control-Request-Methods"
> Wrong CORS Response
> -------------------
>
> Key: STANBOL-616
> URL: https://issues.apache.org/jira/browse/STANBOL-616
> Project: Stanbol
> Issue Type: Bug
> Components: Entity Hub
> Affects Versions: 0.9.0-incubating, 0.10.0-incubating
> Reporter: Sebastian Germesin
> Assignee: Suat Gonul
> Fix For: 0.10.0-incubating
>
>
> I just had a look at the CORS support in Stanbol and I have a question to that.
> In the CORS specification [1], I read that in a CORS request with a preflight the client sets the request header:
> Access-Control-Request-Headers: .... (let's say: origin, content-type, accept)
> Access-Control-Request-Method: .... (let's say: POST)
> and the server (in this case Stanbol) answers with:
> Access-Control-Allow-Headers: ... (let's say: origin, content-type, accept)
> Access-Control-Allow-Origin: ... (let's say: *)
> Access-Control-Allow-Method: (let's say: GET, POST, OPTIONS)
> However, when I perform a query to the Entityhub, e.g., http://dev.iks-project.eu:8081/entityhub/entity/
> Stanbol answers correctly with
> Access-Control-Allow-Headers: origin, content-type, accept
> Access-Control-Allow-Origin: *
> BUT:
>
> Access-Control-Request-Method: GET, POST, OPTIONS
> instead of
> Access-Control-Allow-Method: GET, POST, OPTIONS
> Gladly, for the GET and POST requests that somehow works anyways, but for a PUT and DELETE request
> that fails again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (STANBOL-616) Wrong CORS Response
Posted by "Suat Gonul (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suat Gonul resolved STANBOL-616.
--------------------------------
Resolution: Fixed
> Wrong CORS Response
> -------------------
>
> Key: STANBOL-616
> URL: https://issues.apache.org/jira/browse/STANBOL-616
> Project: Stanbol
> Issue Type: Bug
> Components: Entity Hub
> Affects Versions: 0.9.0-incubating, 0.10.0-incubating
> Reporter: Sebastian Germesin
> Assignee: Suat Gonul
> Fix For: 0.10.0-incubating
>
>
> I just had a look at the CORS support in Stanbol and I have a question to that.
> In the CORS specification [1], I read that in a CORS request with a preflight the client sets the request header:
> Access-Control-Request-Headers: .... (let's say: origin, content-type, accept)
> Access-Control-Request-Method: .... (let's say: POST)
> and the server (in this case Stanbol) answers with:
> Access-Control-Allow-Headers: ... (let's say: origin, content-type, accept)
> Access-Control-Allow-Origin: ... (let's say: *)
> Access-Control-Allow-Method: (let's say: GET, POST, OPTIONS)
> However, when I perform a query to the Entityhub, e.g., http://dev.iks-project.eu:8081/entityhub/entity/
> Stanbol answers correctly with
> Access-Control-Allow-Headers: origin, content-type, accept
> Access-Control-Allow-Origin: *
> BUT:
>
> Access-Control-Request-Method: GET, POST, OPTIONS
> instead of
> Access-Control-Allow-Method: GET, POST, OPTIONS
> Gladly, for the GET and POST requests that somehow works anyways, but for a PUT and DELETE request
> that fails again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira