<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Cross Origin Resource Sharing with Sinatra</title>
	<atom:link href="http://britg.com/2009/12/29/cross-origin-resource-sharing-with-sinatra/feed/" rel="self" type="application/rss+xml" />
	<link>http://britg.com/2009/12/29/cross-origin-resource-sharing-with-sinatra/</link>
	<description>The big yellow one&#039;s the sun.</description>
	<lastBuildDate>Fri, 27 Jan 2012 21:15:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Chris Castle</title>
		<link>http://britg.com/2009/12/29/cross-origin-resource-sharing-with-sinatra/comment-page-1/#comment-544</link>
		<dc:creator>Chris Castle</dc:creator>
		<pubDate>Mon, 04 Jul 2011 04:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://britg.com/?p=1282#comment-544</guid>
		<description>Hey Brit-  Thanks for putting this together.  I&#039;m trying to make an HTTPS cross-domain request with Basic Auth.  I&#039;m using Sinatra (obviously) on the server and jquery on the client.  I&#039;m getting a 401 Unauthorized response from the server.  In looking at the Request headers I don&#039;t see the browser sending the &#039;Authorization&#039; header.  Here are the request and response headers.  Any idea what&#039;s wrong?  If I hit the Request URL by itself in a browser, the auth box pops up, I enter my credentials, and everything works great -- but not when it&#039;s requested via javascript...

Request URL:https://my.site.com/ec2/describe?env=dev&amp;instanceId=i-b285d4dfRequest Method:GETStatus Code:401 UnauthorizedRequest HeadersAccept:*/*Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3Accept-Encoding:gzip,deflate,sdchAccept-Language:en-US,en;q=0.8Connection:keep-aliveHost:my.site.comOrigin:http://localhost:4567Referer:http://localhost:4567/index.htmlUser-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.41 Safari/535.1Query String Parametersenv:devinstanceId:i-b285d4dfResponse HeadersAccess-Control-Allow-Credentials:trueAccess-Control-Allow-Headers:AuthorizationAccess-Control-Allow-Methods:GET, POST, UPDATE, DELETE, OPTIONS, HEADAccess-Control-Allow-Origin:http://localhost:4567Access-Control-Max-Age:1728000Connection:keep-aliveContent-Length:15Content-Type:text/html;charset=utf-8Server:thin 1.2.11 codename Bat-Shit CrazyWWW-Authenticate:Basic realm=&quot;Restricted Area&quot;</description>
		<content:encoded><![CDATA[<p>Hey Brit-  Thanks for putting this together.  I&#8217;m trying to make an HTTPS cross-domain request with Basic Auth.  I&#8217;m using Sinatra (obviously) on the server and jquery on the client.  I&#8217;m getting a 401 Unauthorized response from the server.  In looking at the Request headers I don&#8217;t see the browser sending the &#8216;Authorization&#8217; header.  Here are the request and response headers.  Any idea what&#8217;s wrong?  If I hit the Request URL by itself in a browser, the auth box pops up, I enter my credentials, and everything works great &#8212; but not when it&#8217;s requested via javascript&#8230;</p>
<p>Request URL:<a href="https://my.site.com/ec2/describe?env=dev&#038;instanceId=i-b285d4dfRequest" rel="nofollow">https://my.site.com/ec2/describe?env=dev&#038;instanceId=i-b285d4dfRequest</a> Method:GETStatus Code:401 UnauthorizedRequest HeadersAccept:*/*Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3Accept-Encoding:gzip,deflate,sdchAccept-Language:en-US,en;q=0.8Connection:keep-aliveHost:my.site.comOrigin:<a href="http://localhost:4567Referer:http://localhost:4567/index.htmlUser-Agent:Mozilla/5.0" rel="nofollow">http://localhost:4567Referer:http://localhost:4567/index.htmlUser-Agent:Mozilla/5.0</a> (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.41 Safari/535.1Query String Parametersenv:devinstanceId:i-b285d4dfResponse HeadersAccess-Control-Allow-Credentials:trueAccess-Control-Allow-Headers:AuthorizationAccess-Control-Allow-Methods:GET, POST, UPDATE, DELETE, OPTIONS, HEADAccess-Control-Allow-Origin:<a href="http://localhost:4567Access-Control-Max-Age:1728000Connection:keep-aliveContent-Length:15Content-Type:text/html;charset=utf-8Server:thin" rel="nofollow">http://localhost:4567Access-Control-Max-Age:1728000Connection:keep-aliveContent-Length:15Content-Type:text/html;charset=utf-8Server:thin</a> 1.2.11 codename Bat-Shit CrazyWWW-Authenticate:Basic realm=&#8221;Restricted Area&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: escort services</title>
		<link>http://britg.com/2009/12/29/cross-origin-resource-sharing-with-sinatra/comment-page-1/#comment-490</link>
		<dc:creator>escort services</dc:creator>
		<pubDate>Tue, 01 Mar 2011 14:19:46 +0000</pubDate>
		<guid isPermaLink="false">http://britg.com/?p=1282#comment-490</guid>
		<description>Cross-origin resource sharing Sending messages is not the only solution for sharing information between different websites. The cross-origin resource sharing API loosens the controls over AJAX calls to anywhere but the home domain. ...</description>
		<content:encoded><![CDATA[<p>Cross-origin resource sharing Sending messages is not the only solution for sharing information between different websites. The cross-origin resource sharing API loosens the controls over AJAX calls to anywhere but the home domain. &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

