3 ms·
He was presenting Azure and the browser was enable to parse a XmlHttpRequest. It could be an error on the browser or on the server side application. Because he
by diego_moita 9y ago
He was presenting Azure and the browser was enable to parse a XmlHttpRequest. It could be an error on the browser or on the server side application. Because he is on the server side team he blamed the browser.
Rule #1 of pointing fingers: it's always someone else's fault.
- raverbashing 9y agoFrom the comments on the article, it could also have been a beta version of Edge
- ixxivvix 9y agoWhich is kinda odd to use on a device for presentations, no?
- blinkingled 9y agoThe presenter said it could be because the work laptops are locked down quite a bit. (GPOs to disallow some browser features is not uncommon in corporations at all.)
- Sylos 9y agoWell, he did swap out the client-side and it worked, so that's rather indicative of it not being a server-side problem. Not entirely given, it could be that Chrome happens to implement erronous or non-standards-compliant behaviour which just so happens to match up with the erronous or non-standards-compliant behaviour of the server, but that's starting to get a little far-fetched.