From 1c8ce14b10cf636ed72a9e0ccffedb71143e2e69 Mon Sep 17 00:00:00 2001 From: Scott Jehl Date: Mon, 26 Oct 2015 14:02:13 -0500 Subject: [PATCH] deprecate x-domain hack --- README.md | 23 +---------------------- 1 file changed, 1 insertion(+), 22 deletions(-) diff --git a/README.md b/README.md index 909eb504..d96fe411 100644 --- a/README.md +++ b/README.md @@ -30,28 +30,7 @@ Usage Instructions CDN/X-Domain Setup ====== -Respond.js works by requesting a pristine copy of your CSS via AJAX, so if you host your stylesheets on a CDN (or a subdomain), you'll need to upload a proxy page to enable cross-domain communication. - -See `cross-domain/example.html` for a demo: - -- Upload `cross-domain/respond-proxy.html` to your external domain -- Upload `cross-domain/respond.proxy.gif` to your origin domain -- Reference the file(s) via `` element(s): - -
-	<!-- Respond.js proxy on external server -->
-	<link href="http://externalcdn.com/respond-proxy.html" id="respond-proxy" rel="respond-proxy" />
-
-	<!-- Respond.js redirect location on local server -->
-	<link href="/path/to/respond.proxy.gif" id="respond-redirect" rel="respond-redirect" />
-
-	<!-- Respond.js proxy script on local server -->
-	<script src="/path/to/respond.proxy.js"></script>
-
- -If you are having problems with the cross-domain setup, make sure respond-proxy.html does not have a query string appended to it. - -Note: HUGE thanks to @doctyper for the contributions in the cross-domain proxy! +Respond.js works by requesting a pristine copy of your CSS via AJAX, so if you host your stylesheets on a CDN (or a subdomain), you'll need to set up a local proxy to request the CSS for old IE browsers. Prior versions recommended a deprecated x-domain approach, but a local proxy is preferable (for performance and security reasons) to attempting to work around the cross-domain limitations. Support & Caveats