Thursday, January 15th, 2009
Access Control in IE 8
Category: IE
Related Content:
3.4 rating from 18 votes
Ajax Questions and Answers
Caching and dynamic views
My client does not want to change his cache settings on IE and I'm trying to figure out a way to dynamically update a view each time it is visited. I...
How to change html form tags to ajax
How to change html form tags to...
IE 8 Crashing Problem
Hello Everyone,
Here\'s the situation:
two iSeries boxes - Dev and Prod both V5R4M0
We\'re using AJAX to dynamically load content using a tabbed...
Ajax News, Tips and Guides
Ajax Glossary
Audible Ajax
Episode 25
In Episode 25, we chat about IE 8, standards, Acid3, server side JavaScript, and more.
Podcast RSS
GET E-MAIL UPDATES
Ajaxian Jobs
Contact us
Who are the ajaxians? Find out.
Please contact us at . We would love to hear about any news that we could put up here.
We have individual blogs too:
Feeds
Why didn’t they used the XmlHttpRequest object just like firefox and the others?? Now we have to make two versions, one for IE and one for the others…
Am I alone is really not caring about any IE8 news? I’ve lost so much interest in trying to support IE6 and 7 over Firefox, Safari and Chrome that I no longer care about more junkware eminating from Redmond.
>>Am I alone is really not caring about any IE8 news?
.
All I want from them is to put in the stuff all the other guys have. If all I get is a less-crashy IE7, that’s OK, I guess.
This video could have been shortened by five minutes if he’d just copy and pasted his code in. Instead it’s just a boring piece showing someone typing code. Microsoft could learn something about developer presentations watching the RailsCast videos.
And where is the Safari demo anyway. Is this ‘cool’ stuff really cross-browser compatible, of is Microsoft still in denial that Apple exists?
@spyke
No, you’re not alone. If for nothing else then IE’s *History* I would never again use “features” from IE except for just making sure my stuff at least *works* in IE…
.
6 years with no updates, 10 years with consistently breaking standards and now almost 3 years without pushing IE7 out over automatic Windows Update.
.
Not to mention that all the other browsers are researching into JITing JavaScript and runs a *gazillion* times faster and all that stuff – and a gazillion times more *stable*…!
.
Sorry IE team, it’s probably not your fault, I know. You might be great guys and maybe even great developers – but I COULDN’T CARE LESS…!
The W3C Cross-Site Access Control specification is an important step forward in the evolution of browser applications, and includes a number of different headers, such as:
Access-Control-Allow-Origin
Access-Control-Allow-Headers
Access-Control-Allow-Method
Access-Control-Allow-Credentials
Unfortunately, it appears that the IE8-specific XDomainRequest API does not support all of these features yet. For example, only “GET” and “POST” methods, no application-specific headers and no credentials.
Given that Firefox has demonstrated how to address security concerns and maintain backwards compatibility with same-origin XMLHttpRequest, while adding full support for W3C Cross-Site Access Control, the technical benefit of creating a separate (and incomplete) API for IE8 is unclear. For example, why not complete the feature set, and then rename XDomainRequest to XMLHttpRequest?
Microsoft would gain increased developer goodwill by avoiding such divergence if it is not necessary, but maybe that would make writing Ajax applications too easy. :-)