Since the CORS support in Swift allows the preflight OPTIONS response to be
different on a per-container basis (which is correct in a multi-tenant system),
the CORS support was added directly into Swift's proxy server rather than as
middleware. In order to fulfill the OPTIONS request, container
Keystone doesn't (yet) support CORS - there's an open blueprint for it, but no
work has been applied there as yet
-joe
On Oct 30, 2012, at 10:57 AM, Renier Morales wrote:
> On Oct 30, 2012, at 1:08 PM, David Kranz wrote:
>
>> On 10/30/2012 12:43 PM, Renier Morales wrote:
>>> Hello,
>>>
>>> I
On Oct 30, 2012, at 1:08 PM, David Kranz wrote:
> On 10/30/2012 12:43 PM, Renier Morales wrote:
>> Hello,
>>
>> I'm wondering if someone has already created a nova paste filter/middleware
>> for enabling Cross-Origin Resource Sharing (CORS), allowing a web page to
>> access the openstack api fr
Javier,
Thank you. That sounds good. Actually I would only need to enable CORS on Nova,
Keystone, and Glance. So if you have that and can share it, that would be
perfect for me. Awesome actually :-)
Thanks,
-Renier
On Oct 30, 2012, at 1:08 PM, javier cerviño wrote:
> Hi Renier,
>
>
Hi Renier,
We're currently developing a JavaScript API for Nova, Keystone, and
Glance. To do so we also installed a CORS filter, developed by Adrian
Smith, (with small changes) in these components.
I can pass you the code and a short guideline to configure it if you want.
Cheers,
Javier.
On 30
On 10/30/2012 12:43 PM, Renier Morales wrote:
Hello,
I'm wondering if someone has already created a nova paste
filter/middleware for enabling Cross-Origin Resource Sharing (CORS),
allowing a web page to access the openstack api from another domain.
Any pointers out there?
Thanks,
-Reni
Hello,
I'm wondering if someone has already created a nova paste filter/middleware for
enabling Cross-Origin Resource Sharing (CORS), allowing a web page to access
the openstack api from another domain. Any pointers out there?
Thanks,
-Renier
_
7 matches
Mail list logo