- From: Michael Hausenblas <michael.hausenblas@deri.org>
- Date: Fri, 25 Feb 2011 20:25:43 +0100
- To: Damian Steer <d.steer@bristol.ac.uk>
- Cc: Melvin Carvalho <melvincarvalho@gmail.com>, public-lod@w3.org
> > I tried this recently and it didn't work on either Safari or Chrome > (iirc) without adding: > > Access-Control-Allow-Methods: GET > > Has anyone else had this issue? Hmmm. Unsure, but at least the script I wrote for [1] doesn't seem to require it and I *think* works fine. Would be glad to learn if this is not the case and adapt it respectively. Cheers, Michael [1] http://enable-cors.org/#check -- Dr. Michael Hausenblas, Research Fellow LiDRC - Linked Data Research Centre DERI - Digital Enterprise Research Institute NUIG - National University of Ireland, Galway Ireland, Europe Tel. +353 91 495730 http://linkeddata.deri.ie/ http://sw-app.org/about.html On 25 Feb 2011, at 12:22, Damian Steer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Sorry for changing the topic (and, indeed, sailing off list topic). > > On 24/02/11 18:28, Melvin Carvalho wrote: > >> >> http://www.w3.org/wiki/CORS_Enabled >> >> [reproduced for convenience] ... >> > >> To give Javascript clients basic access to your resources requires >> adding one HTTP Response Header, namely: >> >> Access-Control-Allow-Origin: * >> > > I tried this recently and it didn't work on either Safari or Chrome > (iirc) without adding: > > Access-Control-Allow-Methods: GET > > Has anyone else had this issue? > > Damian > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk1nkNcACgkQAyLCB+mTtynQ4QCfWNSN8IshBfr6ot6XqiO3dxGj > g9UAoLuVH34Pr0aiIyl5HT3RP+Fvo0dZ > =kTBf > -----END PGP SIGNATURE----- >
Received on Friday, 25 February 2011 19:27:17 UTC