ETag headers missing (starting 2015-01-10)

[Wolfram Gürlich]

Is anybody else affected by this strange behavior?

Starting from 2015-01-10 ETag response headers are missing if a request is made from a non-browser user agent like Curl or Go runtime. 

Fetching a file like

curl -vvvv -H 'User-Agent: Nozilla/5' -H 'Accept-Encoding: gzip' http://appstackfive.appspot.com/test.txt > test.txt.gz

shows the faulty behavior. Changing the user agent name from Nozilla to Mozilla fixes things.

Also in cases where the Accept-Encoding header is not present the ETag response header will be gone.

This applies to both http and https request types and also to custom domains. It seems to work with custom domains over HTTPS (SNI) however.

That issue severely hit us in production.  Please star Issue #11593 if you think that it affects you. 

[Jc Lanoë]

I'm experiencing the same issue. Google claims it works for them but no matter what I do, that etag header gets lost along the way.

[Wolfram Gürlich]

My issue report was merged with Issue #11594. So you might want to star it.

[hiroshi saito]

FYI: The issue seems to be fixed at last!
https://code.google.com/p/googleappengine/issues/detail?id=11594#c13

On Tue, Jan 13, 2015 at 10:24 PM, Wolfram Gürlich <w.gue...@gmail.com> wrote:
> My issue report was merged with Issue #11594. So you might want to star it.
>

> --
> 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-appengi...@googlegroups.com.
> To post to this group, send email to google-a...@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/d/optout.