[google-appengine] Re: [cloud-endpoint] [java] deployment and security

Hi Yannick, Namespaces make sense for various environments - Prod / Stage, etc. I'm not 100% clear on the part where I restrict Google Endpoint to serve only the requests coming from domain.com. The thing I am trying to avoid is for "bad guys" calling my API from their machines. I can add

[google-appengine] Re: Serious issues going on with memcache and repeated function calls

Hi, Linus, yes it is, I had some pretty testy issues earlier but it seems ok at the moment, I'll monitor it and see how it goes Cheers On Friday, July 28, 2017 at 11:45:34 PM UTC+3, Richard Cheesmar wrote: > > I am having serious issues with shared memcahce in the python standard > environment

[google-appengine] Re: Serious issues going on with memcache and repeated function calls

Is your app by any chance in europe-west region? There is a thread created today about this, in short we got this answer from Google today: "There was an issue with elevated error rate for Google App Engine Memcache service for European applications which has been resolved for all affected

[google-appengine] Serious issues going on with memcache and repeated function calls

I am having serious issues with shared memcahce in the python standard environment as of today. Even if I flush the cache, the next time I boot, it should fill the cache key, less than 25MB with data, but it seems it is partially filling. I have also noticed some weird behaviour with methods

[google-appengine] Re: [cloud-endpoint] [java] deployment and security

Hello, welcome to the forums. 1) You can choose which URLs you want to restrict in your Java application using security constraints . That way only someone logged in as a developer or your

[google-appengine] Re: Handling API versioning issue

Hi Eric, If you deploy the new API version to the same application version 1, you'll find it under the same 1-dot-xxx address: the one you mention. In such cases, it is more effective to open a bug / issue in the public tracker . The tracker is

[google-appengine] [cloud-endpoint] [java] deployment and security

**Hoping to get some insights from the community. ** With a Google Endpoint version 2 app (Java 8) deployed on GAE, the project becomes available under the url .appspot.com. I had few questions around deployment and security: 1. The URL .appspot.com is accessible by everyone by

[google-appengine] Re: Memcache problems (eu west)

There was an issue with elevated error rate for Google App Engine Memcache service for European applications which has been resolved for all affected projects. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize

[google-appengine] Re: Memcache problems (eu west)

Same on our project. Magically the error disappeared at ~8:30 UTC. Any idea what's the cause of this problem? Am Freitag, 28. Juli 2017 09:28:19 UTC+2 schrieb Linus Larsen: > > Lately I'm getting a lot of these (java, standard env): > >

[google-appengine] Re: Memcache problems (eu west)

Thank's Michael for confirming. I guess then there is some infrastructure work going on. / Linus Den fredag 28 juli 2017 kl. 11:37:24 UTC+2 skrev Michael Steurer: > > Hi Linus, > we have the same problem on a Go standard environment for two days now. It > happens on some requests only but not

[google-appengine] Re: Memcache problems (eu west)

Hi Linus, we have the same problem on a Go standard environment for two days now. It happens on some requests only but not all the time. We have bursts of a few hours, e.g. yesterday from 3pm to 9pm. Best Michael On Friday, July 28, 2017 at 9:28:19 AM UTC+2, Linus Larsen wrote: > > Lately

[google-appengine] Memcache problems (eu west)

Lately I'm getting a lot of these (java, standard env): com.google.appengine.api.memcache.MemcacheServiceApiHelper$RpcResponseHandler handleApiProxyException: Memcache putAll: Unknown exception setting 1 keys: Memcache is temporarily unavailable. (MemcacheServiceApiHelper.java:68