ok, before someone else going crazy on this:
google has changed crossdomain.xml file for youtube api, now instead of using ”*”, it lists TLDs
if you’re testing players from not standard domains (mine was local.lan) or just ip addresses and things just stopped working, now know why.
<!-- http://www.youtube.com/crossdomain.xml --> <!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd"> <cross-domain-policy> <allow-access-from domain="*.youtube.com" /> <allow-access-from domain="s.ytimg.com" /> </cross-domain-policy> <pre /></pre>
What does this mean to an average flash dev?
- Author was Featured
- Bought between 10 and 49 items
- Exclusive Author
- Has been a member for 6-7 years
- Interviewed on the Envato Notes blog
- Item was Featured
- Microlancer Beta Tester
- Referred between 200 and 499 users
TLD -> Top level domain like .com, .net etc.
and this means now you have to generate an API key from your youtube’s account and when you generate that API key you specify the website where you will be going to access youtube videos.
Thanks : I knew what tld was, but didn’t know about the youtube stuff
TLD -> Top level domain like .com, .net etc. and this means now you have to generate an API key from your youtube’s account and when you generate that API key you specify the website where you will be going to access youtube videos.
Sounds pretty bad for the files on sale here. It means that users will need to get a youtube id to run the video players. Strange change on YouTube politics.
i wasn’t clear: what changed is policy to access data API ( gdata.youtube.com) now is restricted to valid domain names while before it was ”*”
so nothing will change for players hosted here but i had a buyer today complaining my player not working on his server, i checked and he was right.
it turned out to be a security violation since he was using IP address, which is not allowed by new crossdomain.