My OperaThe My Opera forums have been replaced with forums.opera.com. Please head over there to discuss Opera's products and features
See the new ForumsYou need to be logged in to post in the forums. If you do not have an account, please sign up first.
HTML5: XMLHttpRequest level 2
Hey! Opera Software!In which epoch we are?
^_^
When we can use Cross-Domain requests?
IE8 even know it!
Originally posted by SowingSadness:
When we can use Cross-Domain requests?
I think you can try cross-domain requests in Opera 12's latest build-
http://snapshot.opera.com/windows/latest
That build added support for CORS and implemented some parts of XMLHttpRequest Level 2.
Windows 7 SP1 x86 edition and Windows XP Service Pack 3.
If you need any help from me with regards to Opera, please make a comment on any of my blog posts.
Support Opera wishes
If you need any help from me with regards to Opera, please make a comment on any of my blog posts.
Support Opera wishes
Me personally - not a fan of cross domain requests.
Opera needs to support it as it is part of html5 but if developing, proxying the request on your server is better for several reasons:
A) You are responsible for the security of your users. With CORS it is possible for an attacker who gained access to remote site or spoofed dns to inject malicious code. With proxy on your server, you can filter for malicious code.
B) If you proxy, you can cache content from the other domain. In many cases this allows you to continue to continue to operate if remote server is down, removing a point of failure that could break functionality of your site.
C) By caching remote content, you use less of their bandwidth.
There probably are appropriate uses for CORS but I would be extremely hesitant to use it myself if I did not admin the cross domain, specifically for the XSS security concerns, I would want to filter the response for any XSS payload before delivering the content to my users.
Just something to think about if you are a web dev.
Opera needs to support it as it is part of html5 but if developing, proxying the request on your server is better for several reasons:
A) You are responsible for the security of your users. With CORS it is possible for an attacker who gained access to remote site or spoofed dns to inject malicious code. With proxy on your server, you can filter for malicious code.
B) If you proxy, you can cache content from the other domain. In many cases this allows you to continue to continue to operate if remote server is down, removing a point of failure that could break functionality of your site.
C) By caching remote content, you use less of their bandwidth.
There probably are appropriate uses for CORS but I would be extremely hesitant to use it myself if I did not admin the cross domain, specifically for the XSS security concerns, I would want to filter the response for any XSS payload before delivering the content to my users.
Just something to think about if you are a web dev.