[
https://issues.apache.org/jira/browse/VYSPER-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-315.
-------------------------------------
Resolution: Not A Problem
BoshServlet already returns the headers for OPTIONS.
Beyond that, the non-BoshServlet requests in the app must already contain the
headers.
So, this is not a BOSH/Vysper problem.
> Support Cross-Origin-Resource-Sharing HTTP Headers
> --------------------------------------------------
>
> Key: VYSPER-315
> URL: https://issues.apache.org/jira/browse/VYSPER-315
> Project: VYSPER
> Issue Type: Bug
> Components: BOSH
> Reporter: Bernd Fondermann
> Fix For: 0.8
>
>
> BOSH can be used in setups where the BOSH webapp is not on the same domain as
> the BOSH server. Browsers have restrictions to not allow AJAX-POST calls
> across origins, which is exactly what BOSH needs in those cases.
> So, today, our BoshServlet supports flxhr (AJAX over Flash) by returning a
> crossdomain.xml file with information about allowed CORS domains.
> Another, more modern and future prove way is to return CORS HTTP Headers, as
> described here:
> http://en.wikipedia.org/wiki/Cross-origin_resource_sharing
--
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
