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 <https://code.google.com/p/googleappengine/issues/detail?id=11593> if you think that it affects you. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
