[google-appengine] charset for static served files
Hi, It seems that both the development server and the production servers by default serves static html files with the "Content-type:text/html" response header. That's fine, except that I'd like a "charset = utf-8" appended to that. The relevant app.yaml entry looks like this: - url: / static_files: index.html upload: index.html it's possible to include the encoding in the html headers with a "Content-Type" meta tag, but I'd like to specify the utf-8 encoding globally, without worrying that some random html file didn't include the header. It's also possible to use a python handler to output the html file and set the encoding explicitly, but then my static files are no longer static, and will incur a higher overhead. So my question is: Can charset be set for static files through app.yaml or some other means? - elias -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Channel API broken in Chrome Extensions
I have the same problem here, trying to use an App Engine Channel from a Chrome extension fails to trigger onmessage/onopen/onerror. Nothing happens, and there's nothing in the extension background page console log. It worked fine a few days ago, and I haven't changed any extension code in that time. Chrome: 10.0.648.204 (stable) on Ubuntu 10.10 - elias On Apr 14, 4:41 pm, RSW wrote: > Hi Moishe, > > I am using the stable release, and the current up-to-date version is > 10.0.648.204 (on a Mac). > > I only use the Channel API within a chrome extension, so I can't say if > there's a problem in other cases. > > -Ronald. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Channel trouble
Hi everyone, I'm currently working on an app engine-based application that uses the Channel feature quite heavily, and the typical user will stay on a channel for quite a while, typically for hours. To work around the 2 hour limit for channel tokens and to handle unstable network connections etc., I've added simple client side JS logic that asks for another channel token and re-connects. However, using the app myself I often (but for from always) experience that the current channel stops receiving messages, without calling onerror nor onclose. For example, I got this from the chrome javascript console today: GET https://758.talkgadget.google.com/talkgadget/dch/bind?VER=8&clid=DE5A9AB046C9D128&gsessionid=PLubLP_rvBwFn5Z_ZIgb_g&prop=data&token=AHRlWrquom9P2cWYEIecxfNDCwg0DhTkEiXg8a9lCtFh9Ken44OvMWkqN6MvsvuswvaCpUqJ3kLEJJHKI5tdiZvZ02WUq-mv9oAVHUMo6EyXsQD1tGQqzmF-saWNlTlOz634n70fugfbHpLVpMwHEtp_XTMGEhmD28R8nids1HdABVQPo7n61YoroahMZZw85LsqOR6Fz5pa&RID=rpc&SID=16398969155EF31&CI=0&AID=339&TYPE=xmlhttp&zx=xoxhjdwthzum&t=1401 (Token timed out.) Without getting a callback to onerror or onclose. "Token timed out" seems like a perfectly normal case, so I wonder why the channel client library doesn't call back. Sometimes, the particular error message is different, but the problem is the same - no callbacks. To paper over the problem, I've implemented a sinple "ping" that requests a Channel message every 5 minutes or so, to check the channel status. This is of course not an acceptable solution, since the point of Channel is fewer rpc calls and timely message delivery. Is there a way to debug this problem further, for example a non-obfusacted version of the channel client library? I can easily do long-running tests since I keep my running all the time anyway, and since I suspect the problem is some odd corner cases. -- 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/-/ZUr9LktEjDoJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
