* Issue summary:* This is hard to describe, because the symptom does not seem to be related to the facts: I have implemented a simple HTTP Server, which sends to the client an HTML page with embedded YouTube IFrame code (Javascript code, loaded asynchronously by the client from 'http://www.youtube.com/iframe_api'). The server runs on my PC (localhost), and clients (both local and remote) execute the page correctly when they receive it. i.e., a YouTube player is loaded with some video and immediately begins to play. I have implemented a similar server with Google App Engine SDK, and tried to run it (again, on my PC). This time, when a client receives the page, the YouTube player begins to load, but then I get a 'Flash crash' report immediately thereafter. In some rare cases, the player completes loading and begins playing the video, so I suspect that it may have something to do with the YouTube Iframe API being loaded asynchronously by the client. I have compared the contents received by the client in both cases (my server and GAE server), and they are identical. So I have no way to explain why the Youtube player would work properly in the first case and fail in the other. * Steps to reproduce issue:* 1. Create an HTML page which uses YouTubeIframeAPI in the simplest manner (as described in the tutorial). 2. Using Google App Engine, Create a Python server which returns this page to the client. 3. Using Google App Engine Launcher, run the server and browse. * Expected output:* The client loads YouTube player and begins to play the video. * Actual results:* A "Flash Crash message appears in most cases. Here is a possible hint to the source of the problem (although it doesn't seem related at first glance): I have noticed another difference in the behavior of the client when the server is implemented with GAE: A special character that I have in the HTML page - (c) - is displayed by the client as a question mark. This does not happen when the server is not implemented with GAE. So this may imply that the problem is in the format of the page sent by the "GAE-implemented" server. If this is indeed the case, then the problem has nothing to do with YouTube IFrame API, and I should "relocate" this bug-report. It would have made sense if the 11-character YouTube Video-ID had contained non-ASCII characters, but as far as I know, it doesn't. I have also posted this in GData-Issues (http://code.google.com/p/gdata-issues/issues/detail?can=2&q=3164&colspec=API%20ID%20Type%20Status%20Priority%20Stars%20Summary&id=3164) Thanks
-- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/sRDXeRhc1zUJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
