CSSHttpRequest (CHR) is a method for cross-domain AJAX using CSS for transport.(nb.io)
nb.io
CSSHttpRequest (CHR) is a method for cross-domain AJAX using CSS for transport.
http://nb.io/hacks/csshttprequest/
13 comments
A beautiful hack was my first thought and then -- ugh, let the exploits begin?
He does say that "Unlike JSONP, untrusted third-party JavaScript cannot execute in the context of the calling page." I'm not sure why, and I would assume that's as long as you never call eval(), but it would be good to know why he thinks this is a more secure idea.
Also didn't see a list of browsers it supports. That would be helpful too. If it's widely supported, this could be a good way to get data feeds from 3rd party sites and not have to do any server-side processing on your end.
Also didn't see a list of browsers it supports. That would be helpful too. If it's widely supported, this could be a good way to get data feeds from 3rd party sites and not have to do any server-side processing on your end.
Looking at his source, he does an eval() in the first line of his response handler for the flickr example. I imagine you could do a JSON.parse() instead of eval() -- preferably! -- but if he says it's secure, what about that line?
They key here though is that evaluating untrusted code from a 3rd party site is not a requirement of the transport. That eval is in the client code and it could just as easily be a safer alternative (either checking that it's sanitary with a regex or using a library's JSON decode function)
With JSONP you necessarily have to execute untrusted code, since JSONP works by loading JavaScript in a <script> tag.
With JSONP you necessarily have to execute untrusted code, since JSONP works by loading JavaScript in a <script> tag.
I see. Thanks for that info, I wasn't familiar with JSONP's technique. In that case, this does sound like a pretty cool library!
> A beautiful hack...
Now we just need someone to encapsulate TCP/IP over it... then maybe DECnet over that...
Now we just need someone to encapsulate TCP/IP over it... then maybe DECnet over that...
Well, the examples don't work on Opera. I know the market share is tiny, but I can't shake the feeling that this is a really fragile method.
yup it needs to work on all browsers realistically. Good attempt though nonetheless.
I think Facebook uses 2 embedded iframes and that I hear works pretty well for security. Is this method documented anywhere?
I used JSONP, but one of the Facebook engineers told me that was a hacky/unsecure method.
I used JSONP, but one of the Facebook engineers told me that was a hacky/unsecure method.
not sure about the facebook method but dojo uses something similar
http://www.sitepen.com/blog/2008/07/30/protected-cross-domai...
http://www.sitepen.com/blog/2008/07/30/protected-cross-domai...
The Flickr tag search example on that page! beautiful!
Cool hack.
Works on IE7, FF3 and Chrome. And as pmjordan said it doesn't work on Opera(I use 9.52).
Works on IE7, FF3 and Chrome. And as pmjordan said it doesn't work on Opera(I use 9.52).
[deleted]
Meanwhile, doing JSONP simply requires the data on the 3rd party server be delivered in a JSON format, while this requires the special 2kb packaging.
Its definitely a more secure way of obtaining remote data from untrusted 3rd parties, but the trade-off is that the 3rd party has to be setup to correctly deliver the data.