(and I realize now that you might have been replying to Kaan.)
On Wednesday, 30 October 2013 18:40:08 UTC-6, Jason Collins wrote:
>
> TIm, the point is that I don't want _any_ branding. I realize that I won't
> be able to project my application branding through the layers, but I want
> Google t
TIm, the point is that I don't want _any_ branding. I realize that I won't
be able to project my application branding through the layers, but I want
Google to replace their branded error screen with a brandless,
black-on-white-text error screen.
j
On Wednesday, 30 October 2013 18:02:23 UTC-6,
You need to consider all the layers involved here.
If the errors occur in infrastructure before it even gets to appengine (and
custom static error pages) then how can you brand the error page,
and something has to be shown.
T
On Thursday, October 31, 2013 1:23:16 AM UTC+8, Jason Collins wrote:
https://code.google.com/p/googleappengine/issues/detail?id=10101&thanks=10101&ts=1381441536
There is also the 500 version of this, that one is accepted with many
replies
tldr, it's a known issue, has been around for very long, not fixed
On Wednesday, October 30, 2013 7:08:44 PM UTC+2, jerome ans
In normal cases it might be a good situation, people could believe that
they are using a Google product :) so If I were google, I wouldn't brand
error pages and put my name on whatever nasty stuff people do
I'm seeing extreme amounts of CloudFlare errors lately, sites go down,
instead of showin
Good to know it's resolved, but the Google-branding is disconcerting. We
whitelabel our products (i.e., our branding cannot show, only our
customers') and go to great lengths for our customers to remove any of our
branding from escaping down the pipe.
Google needs to do the same.
j
On Wednes
This was posted in the Google Page Speed Service forum.
Apprently a temporally connectivity issue.
Should now be resolved.
On 30 October 2013 17:23, Jason Collins wrote:
> We are getting reports of our customers seeing Google-branded 503 error
> screens (attached).
>
> This is a bad thing and
We are getting reports of our customers seeing Google-branded 503 error
screens (attached).
This is a bad thing and needs to be corrected. Usually there is a
non-branded black text on white background error screen for truly
catastrophic issues in the serving infrastructure. Where is the
Google
I just had this problem again a few minutes ago.
On Thursday, June 20, 2013 12:58:17 PM UTC-4, James Gilliam wrote:
>
> Blob upload is failing with 503 (service unavailable) ... see attached
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
In general* you can't.
Instead have a look at
https://developers.google.com/appengine/docs/python/search/
* You can emulate some LIKE queries, notably case-sensitive, prefix queries
(ie BINARY LIKE 'Something%') with range queries, but far from ideal.
On 30 October 2013 12:06, Vijay Kumbh
please help
how to used like query in NDB Datastore
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com.
To post
11 matches
Mail list logo
