I have two webapps WebApp1 and WebApp2 in two different domains. I am setting a cookie in WebApp1 in the HttpResponse. How to read the same cookie from HttpRequest in WebApp2? I know it sounds weird because cookies are specific to a given domain, and we can’t access them from different domains; I’ve however heard … Read more
Ok, think I may have found it: the site runs fine in Chrome’s incognito (porn) mode. So I strongly suspect I’ve got some kind of extension that’s interfering with it (like Do Not Track or something). EDIT It’s Collusion’s “block known tracking sites” feature.
Is your website also on the oxfordlearnersdictionaries.com domain? or your trying to make a call to a domain and the same origin policy is blocking you? Unless you have permission to set header via CORS on the oxfordlearnersdictionaries.com domain you may want to look for another approach.
Sounds like the recommended way to do it is to have your server read the Origin header from the client, compare that to the list of domains you would like to allow, and if it matches, echo the value of the Origin header back to the client as the Access-Control-Allow-Origin header in the response. With .htaccess you can do it like … Read more
Use JSONP. jQuery: PHP: The echo might be wrong, it’s been a while since I’ve used php. In any case you need to output callbackName(‘jsonString’) notice the quotes. jQuery will pass it’s own callback name, so you need to get that from the GET params. And as Stefan Kendall posted, $.getJSON() is a shorthand method, but then you need to … Read more
Access-Control-Allow-Origin is a CORS (Cross-Origin Resource Sharing) header. When Site A tries to fetch content from Site B, Site B can send an Access-Control-Allow-Origin response header to tell the browser that the content of this page is accessible to certain origins. (An origin is a domain, plus a scheme and port number.) By default, Site … Read more