Ajax跨域、Json跨域、Socket跨域和Canvas跨域等同源策略限制的解决方法

前端之家收集整理的这篇文章主要介绍了Ajax跨域、Json跨域、Socket跨域和Canvas跨域等同源策略限制的解决方法前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。

同源是指相同的协议、域名、端口,三者都相同才属于同域。不符合上述定义的请求,则称为跨域。

相信每个开发人员都曾遇到过跨域请求的情况,虽然情况不一样,但问题的本质都可以归为浏览器出于安全考虑下的同源策略的限制。

跨域的情形有很多,最常见的有Ajax跨域、Socket跨域和Canvas跨域。下面列举一些我们常见的跨域情形下,某些浏览器控制台给出的错误提示

FireFox下的提示

已阻止交叉源请求:同源策略不允许读取***上的远程资源。可以将资源移动到相同的域名上或者启用 CORS 来解决这个问题。

Canvas跨域Chrome下的提示

UncaughtSecurityError:Failed to execute'getImageData' on 'CanvasRenderingContext2D':The canvas has been taintedby cross-origin data.

或:

Imagefrom origin 'http://js.xx.com' has been blocked from loading by Cross-OriginResource Sharing policy: No 'Access-Control-Allow-Origin' header is present onthe requested resource. Origin 'http://act.xx.com' is therefore not allowedaccess.


网上有许多解决跨域的方法,大体上有这几种:

1)document.domain+iframe的设置

2)动态创建script

3)利用iframe和location.hash

4)window.name实现的跨域数据传输

5)使用HTML5 postMessage

6)利用flash

7)通过代理,js访问代理,代理转到不同的域

http://developer.yahoo.com/javascript/howto-proxy.html

8)jQuery JSONP(不能成为真正的Ajax,本质上仍是动态创建script)

http://www.cnblogs.com/chopper/archive/2012/03/24/2403945.html

9)跨域资源共享(CORS) 这是HTML5跨域问题的标准解决方

说明:方案1~方案6见Rain Man所写的文章JavaScript跨域总结与解决办法》

http://www.cnblogs.com/rainman/archive/2011/02/20/1959325.html

下面主要就我总结的几种解决跨域的方法,展开说一下。

1) 绕开跨域。

适用情形是:动静分离。

example1.com域名下的页面中跨域请求是以JavaScript内联方式实现的,而请求的目标静态资源是放在example2.com域名下,这时可以将执行跨域请求的JavaScript代码块独立出来,放到example2.com上,而example1.com页面通过外联方式引入该静态域名下的js文件。这样,js与请求的图片等资源都在example2.com下,即可正常访问到。这种方法其实是一种巧妙避开跨域的方法

2) 后台抓取克隆图片

适用情形:动静不分离(两个域名均运行访问静态资源)。

example1.com请求example2.com下的资源图片,可以使用PHP抓取图片并在example2.com下生成一份,这样就可以间接访问到example1.com的静态资源。

html模板示例代码

$("#scratchpad").wScratchPad({ //刮刮卡示例,当前域名http://act.xxx.com

width:283,

height:154,

//color: "#a9a9a7",

image2:"imgdata.PHP?url=http://js.xxx.com/static/activity/sq/guagua315/images/card_inner.jpg",

scratchMove:function() {

}

});

或:

xi=newXMLHttpRequest();

xi.open("GET","imgdata.PHP?url="+yourImageURL,true);

xi.send();

xi.onreadystatechange=function() {

if(xi.readyState==4 && xi.status==200) {

img=newImage;

img.onload=function(){

ctx.drawImage(img, 0,0,canvas.width,canvas.height);

}

img.src=xi.responseText;

}

PHP处理代码

<?PHP//imgdata.PHP

$url=$_GET['url'];

$img =file_get_contents($url);

$imgname = substr(strrchr($url,"/"),1);

file_put_contents($fn,$img);

echo $imgname;

?>

上述代码在当前PHP目录下生成了克隆生成了一张图片

3) 后台程序设置Access-Control-Allow-Origin

适用情形:Ajax获取跨域接口的JSON数据。

example1.com请求example2.com的数据接口,则需要在example2.com的数据接口添加跨域访问授权。

PHP程序中开始出添加header('HeaderName:HeaderValue'); 这样的header标记

header('Access-Control-Allow-Origin:*');

4)修改服务器配置启用CORS

适用情形:跨域访问静态资源。

Access-Control-Allow-Origin是什么作用呢?用于授权资源的跨站访问。比如,静态资源图片都放在example2.com 域名下,如果在返回的头中没有设置 Access-Control-Allow-Origin,那么别的域是没有权限外链你的图片的。

要实现CORS跨域,服务端需要这个一个流程,图片引自html5rocks,附图如下

a.对于简单请求,如GET,只需要在HTTP Response后添加Access-Control-Allow-Origin。

b.对于非简单请求,比如POST、PUT、DELETE等,浏览器会分两次应答。第一次preflight(method: OPTIONS),主要验证来源是否合法,并返回允许的Header等。第二次才是真正的HTTP应答。所以服务器必须处理OPTIONS应答。

这里是一个Nginx启用CORS的参考配置示例http://enable-cors.org/server_nginx.html代码

  1. #
  2. #ACORS(Cross-OriginResouceSharing)configforNginx
  3. #
  4. #==Purpose
  5. #
  6. #ThisNginxconfigurationenablesCORSrequestsinthefollowingway:
  7. #-enablesCORSjustfororiginsonawhitelistspecifiedbyaregularexpression
  8. #-CORSpreflightrequest(OPTIONS)arerespondedimmediately
  9. #-Access-Control-Allow-Credentials=trueforGETandPOSTrequests
  10. #-Access-Control-Max-Age=20days,tominimizerepetitiveOPTIONSrequests
  11. #-varIoUssuperluoussettingstoaccommodatenonconformantbrowsers
  12. #
  13. #==CommentonechoingAccess-Control-Allow-Origin
  14. #
  15. #HowdoyouallowCORSrequestsonlyfromcertaindomains?Thelast
  16. #publishedW3Ccandidaterecommendationstatesthatthe
  17. #Access-Control-Allow-Originheadercanincludealistoforigins.
  18. #(See:http://www.w3.org/TR/2013/CR-cors-20130129/#access-control-allow-origin-response-header)
  19. #However,browsersdonotsupportthiswellanditlikelywillbe
  20. #droppedfromthespec(see,http://www.rfc-editor.org/errata_search.PHP?rfc=6454&eid=3249).
  21. #
  22. #Theusualworkaroundisfortheservertokeepawhitelistof
  23. #acceptableorigins(asaregularexpression),matchtherequest's
  24. #Originheaderagainstthelist,andechobackthematchedvalue.
  25. #
  26. #(Yesyoucanuse'*'toacceptalloriginsbutthisistooopenand
  27. #preventsusing'Access-Control-Allow-Credentials:true',whichis
  28. #neededforHTTPBasicAccessauthentication.)
  29. #
  30. #==Commentonspec
  31. #
  32. #CommentsbelowareallbasedonmyreadingoftheCORSSpecasof
  33. #2013-Jan-29(http://www.w3.org/TR/2013/CR-cors-20130129/),the
  34. #XMLHttpRequestspec(
  35. #http://www.w3.org/TR/2012/WD-XMLHttpRequest-20121206/),and
  36. #experimentationwithlatestversionsofFirefox,Chrome,Safariat
  37. #thatpointintime.
  38. #
  39. #==Changelog
  40. #
  41. #sharedat:https://gist.github.com/algal/5480916
  42. #basedon:https://gist.github.com/alexjs/4165271
  43. #
  44. location/{
  45. #iftherequestincludedanOrigin:headerwithanoriginonthewhitelist,
  46. #thenitissomekindofCORSrequest.
  47. #specifically,thisexampleallowCORSrequestsfrom
  48. #scheme:httporhttps
  49. #authority:anyauthorityendingin".mckinsey.com"
  50. #port:nothing,or:
  51. if($http_origin~*(https?://[^/]*\.mckinsey\.com(:[0-9]+)?)$){
  52. set$cors"true";
  53. }
  54. #Nginxdoesn'tsupportnestedIfstatements,soweusestring
  55. #concatenationtocreateaflagforcompoundconditions
  56. #OPTIONSindicatesaCORSpre-flightrequest
  57. if($request_method='OPTIONS'){
  58. set$cors"${cors}options";
  59. }
  60. #non-OPTIONSindicatesanormalCORSrequest
  61. if($request_method='GET'){
  62. set$cors"${cors}get";
  63. }
  64. if($request_method='POST'){
  65. set$cors"${cors}post";
  66. }
  67. #ifit'saGETorPOST,setthestandardCORSresponsesheader
  68. if($cors="trueget"){
  69. #Tellsthebrowserthisoriginmaymakecross-originrequests
  70. #(Here,weechotherequestingorigin,whichmatchedthewhitelist.)
  71. add_header'Access-Control-Allow-Origin'"$http_origin";
  72. #Tellsthebrowseritmayshowtheresponse,whenXmlHttpRequest.withCredentials=true.
  73. add_header'Access-Control-Allow-Credentials''true';
  74. ##TellthebrowserwhichresponseheaderstheJScansee,besidesthe"simpleresponseheaders"
  75. #add_header'Access-Control-Expose-Headers''myresponseheader';
  76. }
  77. if($cors="truepost"){
  78. #Tellsthebrowserthisoriginmaymakecross-originrequests
  79. #(Here,besidesthe"simpleresponseheaders"
  80. #add_header'Access-Control-Expose-Headers''myresponseheader';
  81. }
  82. #ifit'sOPTIONS,thenit'saCORSpreflightrequestsorespondimmediatelywithnoresponsebody
  83. if($cors="trueoptions"){
  84. #Tellsthebrowserthisoriginmaymakecross-originrequests
  85. #(Here,whichmatchedthewhitelist.)
  86. add_header'Access-Control-Allow-Origin'"$http_origin";
  87. #inapreflightresponse,tellsbrowserthesubsequentactualrequestcanincludeusercredentials(e.g.,cookies)
  88. add_header'Access-Control-Allow-Credentials''true';
  89. #
  90. #Returnspecialpreflightinfo
  91. #
  92. #Tellbrowsertocachethispre-flightinfofor20days
  93. add_header'Access-Control-Max-Age'1728000;
  94. #TellbrowserwerespondtoGET,POST,OPTIONSinnormalCORSrequests.
  95. #
  96. #Notofficiallyneededbutstillincludedtohelpnon-conformingbrowsers.
  97. #
  98. #OPTIONSshouldnotbeneededhere,sincethefieldisused
  99. #toindicatemethodsallowedfor"actualrequest"notthe
  100. #preflightrequest.
  101. #
  102. #GET,POSTalsoshouldnotbeneeded,sincethe"simple
  103. #methods"GET,HEADareincludedbydefault.
  104. #
  105. #Weshouldonlyneedthisheaderfornon-simplerequests
  106. #methods(e.g.,DELETE),orcustomrequestmethods(e.g.,XMODIFY)
  107. add_header'Access-Control-Allow-Methods''GET,OPTIONS';
  108. #Tellbrowserweaccepttheseheadersintheactualrequest
  109. #
  110. #Adynamic,wide-openconfigwouldjustechobackalltheheaders
  111. #listedinthepreflightrequest's
  112. #Access-Control-Request-Headers.
  113. #
  114. #Adynamic,restrictiveconfig,wouldjustechobackthe
  115. #subsetofAccess-Control-Request-Headersheaderswhichare
  116. #allowedforthisresource.
  117. #
  118. #Thisstatic,fairlyopenconfigjustreturnsahardcodedsetof
  119. #headersthatcoversmanycases,includingsomeheadersthat
  120. #areofficiallyunnecessarybutactuallyneededtosupport
  121. #non-conformingbrowsers
  122. #
  123. #Commentonsomeparticularheadersbelow:
  124. #
  125. #Authorization--practicallyandofficiallyneededtosupport
  126. #requestsusingHTTPBasicAccessauthentication.BrowserJS
  127. #canuseHTTPBAauthenticationwithanXmlHttpRequestobject
  128. #reqbycalling
  129. #
  130. #req.withCredentials=true,and
  131. #req.setRequestHeader('Authorization','Basic'+window.btoa(theusername+':'+thepassword))
  132. #
  133. #Counterintuitively,theusernameandpasswordfieldson
  134. #XmlHttpRequest#opencannotbeusedtosettheauthorization
  135. #fieldautomaticallyforCORSrequests.
  136. #
  137. #Content-Type--thisisa"simpleheader"onlywhenit's
  138. #valueiseitherapplication/x-www-form-urlencoded,
  139. #multipart/form-data,ortext/plain;andinthatcaseitdoes
  140. #notofficiallyneedtobeincluded.But,ifyourbrowser
  141. #codesetsthecontenttypeasapplication/json,forexample,
  142. #thenthatmakestheheadernon-simple,andthenyourserver
  143. #mustdeclarethatitallowstheContent-Typeheader.
  144. #
  145. #Accept,Accept-Language,Content-Language--thesearethe
  146. #"simpleheaders"andtheyareofficiallynever
  147. #required.Practically,possiblyrequired.
  148. #
  149. #Origin--logically,shouldnotneedtobeexplicitly
  150. #required,sinceit'simplicitlyrequiredbyallof
  151. #CORS.officially,itisunclearifitisrequiredor
  152. #forbidden!practically,probablyrequiredbyexisting
  153. #browsers(GeckodoesnotrequestitbutWebKitdoes,so
  154. #WebKitmightchokeifit'snotreturnedback).
  155. #
  156. #User-Agent,DNT--officially,shouldnotberequired,as
  157. #theycannotbesetas"authorrequestheaders".practically,
  158. #mayberequired.
  159. #
  160. #MyComment:
  161. #
  162. #Thespecsarecontradictory,orelsejustconfusingtome,
  163. #inhowtheydescribecertainheadersasrequiredbyCORSbut
  164. #forbiddenbyXmlHttpRequest.TheCORSSpecsaysthebrowser
  165. #issupposedtosetAccess-Control-Request-Headerstoinclude
  166. #only"authorrequestheaders"(section7.1.5).Andthenthe
  167. #serverissupposedtouseAccess-Control-Allow-Headersto
  168. #echobackthesubsetofthosewhichisallowed,tellingthe
  169. #browserthatitshouldnotcontinueandperformtheactual
  170. #requestifitincludesadditionalheaders(section7.1.5,
  171. #step8).Sothisimpliesthebrowserclientcodemusttake
  172. #caretoincludeallnecessaryheadersasauthorrequest
  173. #headers.
  174. #
  175. #However,thespecforXmlHttpRequest#setRequestHeader
  176. #(section4.6.2)providesalonglistofheaderswhichthe
  177. #thebrowserclientcodeisforbiddentoset,includingfor
  178. #instanceOrigin,DNT(donottrack),User-Agent,etc..This
  179. #isunderstandable:theseareallheadersthatwewantthe
  180. #browseritselftocontrol,sothatmalicIoUsbrowserclient
  181. #codecannotspoofthemandforinstancepretendtobefroma
  182. #differentorigin,etc..
  183. #
  184. #ButifXmlHttpRequestforbidsthebrowserclientcodefrom
  185. #settingthese(aspertheXmlHttpRequestspec),thenthey
  186. #arenotauthorrequestheaders.Andiftheyarenotauthor
  187. #requestheaders,thenthebrowsershouldnotincludethemin
  188. #thepreflightrequest'sAccess-Control-Request-Headers.And
  189. #iftheyarenotincludedinAccess-Control-Request-Headers,
  190. #thentheyshouldnotbeechoedby
  191. #Access-Control-Allow-Headers.Andiftheyarenotechoedby
  192. #Access-Control-Allow-Headers,thenthebrowsershouldnot
  193. #continueandexecuteactualrequest.Sothisseemstoimply
  194. #thattheCORSandXmlHttpRequestspecsforbidcertain
  195. #widely-usedfieldsinCORSrequests,includingtheOrigin
  196. #field,whichtheyalsorequireforCORSrequests.
  197. #
  198. #Thebottomline:itseemsthereareheadersneededforthe
  199. #webandCORStowork,whichatthemomentyoushould
  200. #hard-codeintoAccess-Control-Allow-Headers,although
  201. #officialspecsimplythisshouldnotbenecessary.
  202. #
  203. add_header'Access-Control-Allow-Headers''Authorization,Content-Type,Accept,Origin,DNT,Cache-Control,X-Mx-ReqToken,Keep-Alive,X-Requested-With,If-Modified-Since';
  204. #buildentireresponsetothepreflightrequest
  205. #nobodyinthisresponse
  206. add_header'Content-Length'0;
  207. #(shouldnotbenecessary,butincludedfornon-conformingbrowsers)
  208. add_header'Content-Type''text/plaincharset=UTF-8';
  209. #indicatesuccessfulreturnwithnocontent
  210. return204;
  211. }
  212. #--PUTYOURREGULARNginxCODEHERE--
  213. }

服务器解析流程如下:

a.首先查看http头部有无origin字段;

b.如果没有,或者不允许,直接当成普通请求处理,结束;

c.如果有并且是允许的,那么再看是否是preflight(method=OPTIONS);

d.如果是preflight,就返回Allow-Headers、Allow-Methods等,内容为空;

e.如果不是preflight,就返回Allow-Origin、Allow-Credentials等,并返回正常内容

若服务器为Nginx,可以 Nginx conf 文件中加入以下内容

  1. location/{
  2. add_headerAccess-Control-Allow-Origin*;
  3. }

若服务器为Apache,则可以按照如下配置:

  1. <IfModulemod_setenvif.c>
  2. <IfModulemod_headers.c>
  3. <FilesMatch"\.(cur|gif|ico|jpe?g|png|svgz?|webp)$">
  4. SetEnvIfOrigin":"IS_CORS
  5. HeadersetAccess-Control-Allow-Origin"*"env=IS_CORS
  6. </FilesMatch>
  7. </IfModule>
  8. </IfModule>

为安全起见,Access-Control-Allow-Origin也可设为特定域名的方式。

在HTML5中,有些HTML元素为CORS提供了支持,如img、video新增了crossOrigin属性属性值可以为anonymoususe-credentials。比如,canvas绘图要用到跨域图片,在JavaScript中要设置img.crossOrigin="Anonymous";

[javascript] view plain copy
  1. varimg=newImage,
  2. canvas=document.createElement("canvas"),
  3. ctx=canvas.getContext("2d"),
  4. src="http://example.com/image";//insertimageurlhere
  5. img.crossOrigin="Anonymous";
  6. img.onload=function(){
  7. canvas.width=img.width;
  8. canvas.height=img.height;
  9. ctx.drawImage(img,0);
  10. localStorage.setItem("savedImageData",canvas.toDataURL("image/png"));
  11. }
  12. img.src=src;
  13. //makesuretheloadeventfiresforcachedimagestoo
  14. if(img.complete||img.complete===undefined){
  15. img.src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///ywAAAAAAQABAAACAUwAOw==";
  16. img.src=src;
  17. }

上述配置完成后,重启服务器,CORS启用。

然后我们再刷新页面查询请求头的参数,可以发现多出一个:Access-Control-Allow-Origin:*

,到此证明服务器配置已经生效。同时我们的canvas绘图也可以正常使用了。

刷新页面返回请求响应结果后,HTTP Request Headers的内容

Remote Address:222.132.18.xx:80

Request URL:http://js.xx.com/static/activity/sq/guagua315/images/card_inner.jpg

Request Method:GET

Status Code:200 OK

Request Headersview source

Accept:image/webp,*/*;q=0.8

Accept-Encoding:gzip,deflate,sdch

Accept-Language:zh-CN,zh;q=0.8

Cache-Control:no-cache

Connection:keep-alive

Host:js.xx.com

Origin:http://act.xx.com

Pragma:no-cache

RA-Sid:7CCAD53E-20140704-054839-03c57a-85faf2

RA-Ver:2.8.8

Referer:http://act.xx.com/sq/guagua315?uuid=46124642&fid=2&sign=xxx

User-Agent:Mozilla/5.0 (Windows NT 6.1;WOW64) AppleWebKit/537.36 (KHTML,like Gecko) Chrome/40.0.2214.115Safari/537.36

Response Headersview source

Accept-Ranges:bytes

Access-Control-Allow-Origin:*

Connection:close

Content-Length:4010

Content-Type:image/jpeg

Date:Thu,12 Mar 2015 02:29:43 GMT

ETag:"54f7d1b4-faa"

Last-Modified:Thu,05 Mar 2015 03:47:00 GMT

Powered-By-ChinaCache:MISS fromCNC-WF-3-3X6

Powered-By-ChinaCache:MISS fromCNC-WF-3-3X5

Server:Tengine

Switch:FSCS

附图:


参考文章

CORS enabled image https://developer.mozilla.org/en-US/docs/Web/HTML/CORS_enabled_image

CORS on Nginx http://enable-cors.org/server_nginx.html

Nginx CORS实现JS跨域 http://www.jb51.cc/article/p-xhzdhafc-bbp.html

转载请注明出处,文章来自于freshlover的CSDN空间《Ajax跨域、Json跨域、Socket跨域和Canvas跨域等同源策略限制的解决方法

http://www.jb51.cc/article/p-dsqvmmtq-yn.html

猜你在找的Ajax相关文章