<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Mon, 20 May 2013 00:14:06 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[David M&uuml;ller: Cross Domain AJAX Guide]]></title>
      <guid>http://www.phpdeveloper.org/news/18868</guid>
      <link>http://www.phpdeveloper.org/news/18868</link>
      <description><![CDATA[<p>
In his latest post <i>David M&uuml;ller</i> covers some of the things to consider when <a href="http://www.d-mueller.de/blog/cross-domain-ajax-guide/">working with cross-domain ajax requests</a> including CORS and iframes.
</p>
<blockquote>
As it is widely known, AJAX Requests are only possible if port, protocol and domain of sender and receiver are equal. [...] Having this cleared out, we will cover ways around this restriction.
</blockquote>
<p>
He covers three main approaches to allowing these cross-domain requests (and some of the security implications that can come with them):
</p>
<ul>
<li>CORS (Cross Origin Resource Sharing)
<li>JSONP (Javascript with a local domain callback)
<li>Iframes
</ul>
<p>
He also briefly mentions things like <a href="https://developer.mozilla.org/en-US/docs/DOM/window.postMessage">window.postMessage</a> (HTML5) and the use of a backend script to proxy a request into your application's local code. 
</p>]]></description>
      <pubDate>Mon, 10 Dec 2012 12:17:39 -0600</pubDate>
    </item>
  </channel>
</rss>
