<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #crossdomain</title>
    <link>/tags/crossdomain/</link>
    <description>Recent bookmarks tagged #crossdomain</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:55 +0000</lastBuildDate>
    <item>
      <title>Cross-domain Ajax with Cross-Origin Resource Sharing | NCZOnline</title>
      <link>http://www.nczonline.net/blog/2010/05/25/cross-domain-ajax-with-cross-origin-resource-sharing</link>
      <description>&#34;A couple of years ago, web developers were banging their head against the first wall in Ajax: the same-origin policy. While we marveled at the giant step forward enabled by cross-browser support for the XMLHttpRequest object, we quickly bemoaned the fact that there was no way to make a request to a different domain from JavaScript. Everyone setup proxies on their web sites, which was the onset of a new host of open redirect problems, as a way to get around the restriction. Although developers were working around this limitation using server-side proxies as well as other techniques, the community outcry was around allowing native cross-domain Ajax requests. A lot of people are unaware that almost all browsers (Internet Explorer 8+, Firefox 3.5+, Safari 4+, and Chrome) presently support cross-domain Ajax via a protocol called Cross-Origin Resource Sharing.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #ajax #cors #crossdomain #security #webdev&lt;/p&gt;</description>
      <pubDate>Tue, 13 Jul 2010 18:29:20 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:13743</guid>
      <category>ajax</category>
      <category>cors</category>
      <category>crossdomain</category>
      <category>security</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
