[google-appengine] Re: no response headers from Google Frontend (or not paying for them), denial of wallet attacks

as you mentioned it may DDos attack, please go cloud console to file support case, it will allow us to look into the issue specific based on your logs and service behavior, to assist you fix the issue. On Wednesday, June 16, 2021 at 3:03:59 AM UTC-4 waltrau...@gmail.com wrote: > Hi! > Thanks

Re: [google-appengine] Re: Google App Engine - Split Traffic and promote

Oh thanks George! Either I use two services of the same code base one for prod and one for staging. Or opt for two projects, one for prod and the other for staging? Then, traffic splitting works against a single service (without the version specified in the URL). In other words, traffic is split

[google-appengine] Re: Google App Engine - Split Traffic and promote

Hello, You are right, you can use traffic splitting to specify a percentage distribution of traffic across two or more of the versions within a service, as detailed on the "Split Traffic" page . Deploying with --promot

Re: [google-appengine] Google App Engine - Split Traffic and promote

Thanks, Patrice, for the valuable information. In practice, I test and verify Staging. Once we are happy with it, we merge the "develop" branch on the "main" branch and then production takes the latest changes. However, with versions, every new build of the app, could be a new version. Instead of

[google-appengine] Re: The /app/bootstrap/cache directory must be present and writable.

Hello George, Can you confirm that this issue is now solved? Kind regards. On Monday, June 14, 2021 at 7:34:05 PM UTC+2 bha...@gmail.com wrote: > Hi George, > > I wasn't able to understand what happened to be honest! I reverted a few > commits, and it works again. I must have messed with the v

[google-appengine] Re: no response headers from Google Frontend (or not paying for them), denial of wallet attacks

Hi! Thanks for the reply. The incoming request headers are somewhat manipulated and you are right, for instance "X-Forwarded-For" is added and as a service to my app, it tells me the source request ip address. Then my app and my jetty web server handles the request. I remove all response headers