[google-appengine] Re: Should I take my website somewhere else? - blocked in China
As I know, *.appspot.com mostly works in China, only completely blocked for a short period early this year, after that only some apps -- most proxies which can be used to access other blocked sites -- are still blocked. And for the custom domain, some Chinese developers will find available ips of ghs.google.com and set up their own ghs.***.***, which usually finally results in that ip blocked, too. On 4月10日, 上午8时08分, WallyDD shaneb...@gmail.com wrote: Hi TJ, That really is an amazing post. I'm impressed, you have certainly covered all the technical bases of implementing a proxy. My biggest concern is that Googles behaviour is unpredictable and I not entirely sure how well they will respond to something like this being implemented. 1. I have experienced being blocked by the app engine (try again in an hour etc.), so I could reasonably assume that it would be likely that a lot of traffic coming from one source may be blocked. 2. A large portion of the revenue comes from Google adsense/adwords. Google uses a variety of mechanisms to check for invalid clicks, so all the clicks coming from one source would no doubt raise some red flags. 3. The traffic statistics would be almost useless (there is probably a workaround... but a lot of work). 4. Google has deliberately and intentionally blocked traffic originating from Sudan, Syria, Cuba, Iran and North Korea(not really sure if they have internet there). From the legal discourse I have read it would appear google is obligated to block any proxies where traffic is coming from these countries. I don't really understand this one as the USA changed their political administration in January 2009 and the block went in two weeks later. There has to be some politics behind this which I am unaware of. Google has decided to say nothing on this subject so I can only assume the worst. Google has also said nothing about the China block, which again means to expect the worst. I am also far from convinced that Google has figured out China (like a lot of western companies). From the look of their developer bloghttp://www.developer.googlechinablog.com/, only 16 people read this as the RSS feed. I can't really expect any Chinese to have faith in Google with not only that their country has blocked, but more importantly that google itself has actively blocked other countries. Google will do what Google wants to do and fail to communicate. I can't see this strategy doing anything other than annoying the Chinese further. And back to China I go next week (luckily on unrelated business). And TJ, I like your post, if I can get some (positive) answers I will be putting in a proxy just as you have outlined. Keep up the great work. On Apr 9, 10:35 am, T.J. Crowder t...@crowdersoftware.com wrote: Hi Wally, Sorry to hear about the block. The internet is indeed a funny place. I did respond with a question on how to set this up but have received no answer? Any ideas anyone? Setting up a proxy server is a non-trivial task (I'm not saying it's hard, just non-trivial) so you're not likely to get a lot of dedicated help for it here. May be worth seeking out other newsgroups for the technical details (if you haven't already!). Most commercial-grade web software such as Apache[1] or nginx[2] can be set up to proxy, and there are several dedicated proxy packages as well (such as Squid[3]). I've been hearing very good things about nginx the last year or so, but have virtually no direct experience with it (and not that much experience setting up proxies at all, so take all of this with a grain of salt). [1]http://httpd.apache.org/ [2]http://nginx.net/ [3]http://www.squid-cache.org/ But since you'll need a hosting provider of some sort for the proxy, and it sounds as though this is going to be your main reason for having that other hosting service, it may be worth considering approaching hosting providers who will set up and maintain the proxy for you, rather than doing it yourself. I searched for proxy hosting and there's a whole industry out there you can tap into. It depends on whether this is something you want to add to your set of skills. Naturally, you'll want to be sure that the proxy hosting company itself isn't blocked in China! Given what they do, I suspect a fair number of them are, but the censors can't keep on top of all of them, and you can switch as necessary (the joys of proxying!). A downside of the proxy approach is that you'll end up paying anywhere from twice to six times as much for at least some of your site's traffic -- the parts that can't be cached. Say you host the proxy at Acme Hosting Company. Where before your traffic costs on a request for dynamic content were: * Inbound cost at AppEngine (receiving request from end user's browser) * Outbound cost at AppEngine (sending reply to end user's browser) with a proxy you'll be
[google-appengine] Re: App Engine blocked in China, what to do?
It is said that the ip of ghs.google.com is blocked. On 1月5日, 上午2时28分, Nick Winter livel...@gmail.com wrote: skrit.appspot.com works, but according to our users andhttp://www.websitepulse.com/help/testtools.china-test.htmlit's still blocked atwww.skritter.com. Are you accessinghttp://skrit.appspot.com orhttp://www.skritter.com? --~--~-~--~~~---~--~~ 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] Re: Expires header for zipserve files?
change this: - url: /images/.* script: $PYTHON_LIB/google/appengine/ext/zipserve to - url: /images/.* script: main.py # this could be other script, e.g. zipserve.py then have a look at: http://code.google.com/p/googleappengine/source/browse/trunk/google/appengine/ext/zipserve/__init__.py#36 and edit your main.py and don't forget to include this in your main.py: from google.appengine.ext import zipserve On 11月19日, 下午1时45分, Adam Fisk [EMAIL PROTECTED] wrote: Is there any way to set an expires header for files served with google/ appengine/ext/zipserve? I've got expires working for static content and within Django, but the zipserve files are slipping through my fingers. Thanks. -Adam Fisk --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Should I use the development console online?
In fact, I tried using it, but it stopped to work since some days ago, always showing: 500 BadRequestError: app application-id cannot call GetSchema I searched the group, and found an early post at: http://groups.google.com/group/google-appengine/msg/e770ceefa2c26d54 where Marzia said: The admin is meant only for use with the development web server. For your deployed application, visit http://appengine.google.com and sign in with your administrator account to view your logs, datastore, and administrative information. but the docs at: http://code.google.com/appengine/docs/configuringanapp.html#Referring_to_the_Python_Library_Directory it says: For example, $PYTHON_LIB/google/appengine/ext/admin is an administrative application similar to the developer console feature of the development web server that can run as part of your application on App Engine itself. To set it up, ... So which one is right? Thanks. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Should I use the development console online?
Thanks! On 10月11日, 上午12时33分, Marzia Niccolai [EMAIL PROTECTED] wrote: Hi, A recent change to the admin module introduced an error that breaks the SDK admin console when running on App Engine. The advantage to running the SDK admin console on App Engine is to have an interactive Python console to run one off queries/commands (this is why the admin modules must be restricted to admin only login!). I would suggest uploading shell.py with your app to run interctive commands, and use the App Engine Admin Console to view the datastore. shell.py can be downloaded here:http://code.google.com/p/google-app-engine-samples/ Give it a test run at:http://shell.appspot.com -Marzia On Fri, Oct 10, 2008 at 4:52 AM, Hector Zhao [EMAIL PROTECTED] wrote: In fact, I tried using it, but it stopped to work since some days ago, always showing: 500 BadRequestError: app application-id cannot call GetSchema I searched the group, and found an early post at: http://groups.google.com/group/google-appengine/msg/e770ceefa2c26d54 where Marzia said: The admin is meant only for use with the development web server. For your deployed application, visit http://appengine.google.comand sign in with your administrator account to view your logs, datastore, and administrative information. but the docs at: http://code.google.com/appengine/docs/configuringanapp.html#Referring... it says: For example, $PYTHON_LIB/google/appengine/ext/admin is an administrative application similar to the developer console feature of the development web server that can run as part of your application on App Engine itself. To set it up, ... So which one is right? Thanks. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
