[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] Difference in CORS implementation between Firefox and Chrome




On 02/08/11 09:56 PM, Kenneth Russell wrote:
I haven't checked exactly what the site does, but could this be an issue?

https://bugs.webkit.org/show_bug.cgi?id=64813

Basically, if the response headers contain
"Access-Control-Allow-Origin: *", then WebKit will force a reload of
the resource if it was originally fetched with a normal image request,
and subsequently fetched via CORS. (The reload is usually satisfied by
the disk cache.)

Thanks for the pointer. I know that one reason why it took us a long time to get CORS support was exactly this kind of issues with the image cache. I'll check that we pass your test.



This was a pretty recent bug fix / workaround in WebKit. Chrome 13 doesn't contain the fix, so if Chrome 13 exhibits the same behavior as Firefox, it's likely the issue.

Chrome 13.0.782.107 renders the textures normally, like Chrome 14. So this seems to be a different issue.


Benoit


WebKit still has some incorrect behavior if the Access-Control-Allow-Origin response header contains a specific domain or list of domains, regardless of whether the response headers also contain "Vary: Origin". The current conventional wisdom is to configure the server to return "Access-Control-Allow-Origin: *" all the time for unsecured, public content.

-Ken

On Tue, Aug 2, 2011 at 6:41 PM, Benoit Jacob<bjacob@mozilla.com> wrote:

Hi,

This page:

http://www.mapcrunch.com/gallery?webgl=1

uses cross-domain images as textures served, if I understand correctly, by
Google Maps. The textures render normally in Chrome 14, but are blocked as
illegal cross-domain textures in Firefox.

Since it renders normally in Chrome 14 that must mean that it uses CORS. So
there must be a bug in the CORS implementation of at least one browser here.

Before I investigate this further I wanted to ask if this rings a bell?

Thanks
Benoit

-----------------------------------------------------------
You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl
-----------------------------------------------------------




-----------------------------------------------------------
You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl
-----------------------------------------------------------