Comments on: Abrupt YouTube security policy change http://joeberkovitz.com/blog/2006/12/14/abrupt-youtube-security-policy-change/ Just another WordPress weblog Sat, 13 Mar 2010 04:05:42 -0500 http://wordpress.org/?v=2.8.5 hourly 1 By: Flex Youtube Grabber http://joeberkovitz.com/blog/2006/12/14/abrupt-youtube-security-policy-change/comment-page-1/#comment-73 Flex Youtube Grabber Fri, 27 Apr 2007 15:56:45 +0000 http://www.joeberkovitz.com/blog/?p=36#comment-73 [...] They are obviously not using the Youtube API because Youtube blew that up by changing making a security policy change to the crossdomain.xml file needed to pull videos into Flex.   So I did a little investigation.  I found a site, in French, that had a Flash 8 application to basically screen scrape and decode the URL to Youtube videos.   I migrated this over to Flex and created a small demo application.   [...] [...] They are obviously not using the Youtube API because Youtube blew that up by changing making a security policy change to the crossdomain.xml file needed to pull videos into Flex.   So I did a little investigation.  I found a site, in French, that had a Flash 8 application to basically screen scrape and decode the URL to Youtube videos.   I migrated this over to Flex and created a small demo application.   [...]

]]> By: Abrupt YouTube security policy change « FLEXing My Muscle http://joeberkovitz.com/blog/2006/12/14/abrupt-youtube-security-policy-change/comment-page-1/#comment-72 Abrupt YouTube security policy change « FLEXing My Muscle Tue, 27 Mar 2007 18:26:21 +0000 http://www.joeberkovitz.com/blog/?p=36#comment-72 [...] Possibly due to an exploit, youTube abruptly changed their crossdomain.xml file to only allow access from the youtube.com domain. As a result, YouTube developer API calls no longer work if the SWF exists in a non-youtube.com domain. You can read more on this on Joe’s Blog here. [...] [...] Possibly due to an exploit, youTube abruptly changed their crossdomain.xml file to only allow access from the youtube.com domain. As a result, YouTube developer API calls no longer work if the SWF exists in a non-youtube.com domain. You can read more on this on Joe’s Blog here. [...]

]]>