Talk:Cross-origin resource sharing

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Server Side Control vs. Browser Side Control[edit]

CORS should be a control at the browser side, but it went to the wrong way, it got to the server side. More specifically, when you are at http://www.1st.com/sthFrom1st.html, you want to access http://www.2nd.com/otherthing.html with javascript or java applet. Your browser will not allow this because of the "same origin policy". Now to extend this, it is also a policy for the browser, then why get into the server side to control the server? Got crazy? CORS is a control at the server side http://www.2nd.com which is different from www.1st.com.

The webpage sthFrom1st.html needs to tell the web browser what sites can be deemed as the same origin.

In fact, I think that this is easy to specify. In the html head, we can specify additional domains should be allowed to access. Browsers read these, then the original domain and the additional domains are all deemed to be the same origin. Currently, it is the browser block us. I am at http://1st.com/a.html, then I access http://2nd.com/d.html, with ajax or xmlhttprequest, use firefox, I can clearly see that the remote server returns everything, and everything is good. but the browser does not allow me to access the content.

http://www.w3.org/TR/html40/struct/links.html#edef-LINK

Jackzhp (talk) 23:58, 25 June 2011 (UTC)

This is not the right place for discussing the future of browser technology. I suggest you bring your use case and proposal to the mailing list of the Web Applications Working Group of W3C, where CORS, the specification of Cross Domain control in your terminology and the subject of this entry, is being developed. I'll delete your section for the moment as "we" (and also future stuff) is fairly rare in Wikipedia. — Kennyluck (talk) 22:29, 27 June 2011 (UTC)

Requested move[edit]

The following discussion is an archived discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.

The result of the move request was: moved to Cross-origin resource sharing. Favonian (talk) 22:08, 16 February 2012 (UTC)


Cross-Origin Resource SharingCross-origin resource sharing – Sentence case. http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style#Article_titles XP1 (talk) 13:27, 9 February 2012 (UTC)

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.

URLs in examples[edit]

The following URL, used in the "simple example" section, does not follow best standard practice. As per RFC 2606:

 http://www.example-social-network.com

should be:

 http://social-network-service.example.com

— Preceding unsigned comment added by 190.18.14.46 (talk) 16:08, 1 January 2013 (UTC)

Orphaned references in Cross-origin resource sharing[edit]

I check pages listed in Category:Pages with incorrect ref formatting to try to fix reference errors. One of the things I do is look for content for orphaned references in wikilinked articles. I have found content for some of Cross-origin resource sharing's orphans, the problem is that I found more than one version. I can't determine which (if any) is correct for this article, so I am asking for a sentient editor to look it over and copy the correct ref content into this article.

Reference named "ars-blink":

I apologize if any of the above are effectively identical; I am just a simple computer program, so I can't determine whether minor differences are significant or not. AnomieBOT 03:51, 30 August 2015 (UTC)