5 ms·
Wrong conclusion. The kludge is making cross origin requests in the first place.
by stefan_ 7y ago
Wrong conclusion. The kludge is making cross origin requests in the first place.
- anaphor 7y agoMaybe, but people want to write applications that can easily interact with each other in a secure way. Trying to do that when your browser implicitly authorizes you no matter what the origin of a request is makes that extraordinarily difficult to do safely. Adding in the backwards compatibility problem makes it even worse because any solution is going to have to work with the existing methods.
- deleted 7y ago[deleted]
- modethirteen 7y agoCross origin requests are legitimate in some use cases. I outline one here: https://news.ycombinator.com/item?id=20405275 https://news.ycombinator.com/item?id=20405275 TL;DR Hosting cross domain web widgets or customer engagement experiences like chat windows, etc
- jandrese 7y agoWhat's the alternative? The webserver requests the third party resources on your behalf and repackages them into its own response?
- JTbane 7y agoYou should be able to make REST requests anywhere, without caring about origin.