Hey Attila, Not to worry - if you can even manage to capture some of the details given, such as the request/response of a sample incident, the URL, etc., that could be enough. We have had issue reports of requesting gzip and not receiving it, but as far as I know, this has not been reported. It's worth mentioning that it technically follows the RFC doc <https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html>:
If no Accept-Encoding field is present in a request, the server MAY assume > that the client will accept any content coding. In this case, if "identity" > is one of the available content-codings, then the server SHOULD use the > "identity" content-coding, unless it has additional information that a > different content-coding is meaningful to the client. So, setting "accept-encoding: identity" for curl should resolve this. Cheers! Nick Cloud Platform Community Support On Saturday, July 9, 2016 at 1:27:18 AM UTC-4, Attila-Mihaly Balazs wrote: > > Hello, > > Unfortunately I'm not able to reproduce this reliably (in fact I tried to > repro yesterday before posting this message). If I manage a repro, I'll be > sure to post a bug report (although, given how my last bug report about > memory corruption on PHP instances fared I have no great hope) and also > update this thread. > > Regards, > Attila > > On Friday, 8 July 2016 22:06:47 UTC+3, Nick (Cloud Platform Support) wrote: >> >> Hey Attila, >> >> An issue report like this should be posted to the Public Issue Tracker >> for App Engine, <http://code.google.com/p/googleappengine/issues/list> >> with some more details necessary to determine exactly what's happening: >> >> 1. The exact URL and resource type that this was observed for >> 2. Example request/response >> >> This is necessary so we can attempt to determine what's happening and >> also so that we can attempt to reproduce the same behaviour from our own >> side. >> >> When you make a report there, feel free to link it here and I'll be happy >> to take a look - we monitor the Issue Trackers daily, so it wouldn't take >> long to hear a response on your report anyways. >> >> Cheers! >> >> Nick >> Cloud Platform Community Support >> >> On Friday, July 8, 2016 at 9:16:25 AM UTC-4, Attila-Mihaly Balazs wrote: >>> >>> Hello, >>> >>> This is something which I'm able to reproduce occasionally: for static >>> content deployed on google app engine the frontend / edge cache sometimes >>> serves the content gzipped even if the client doesn't ask for it (ie. it >>> doesn't send an "Accept-Encoding" header). My application is deployed in >>> the EU region. This isn't generally a problem since most (all?) browsers >>> send Accept-Encoding: deflate, gzip, however cURL doesn't by default (only >>> if you specify --compressed). >>> >>> Perhaps the URL was first accessed by a browser supporting gzip, it was >>> cached in the compressed format and is being (erroneously) served this way? >>> Note: even when the response is unexpectedly compressed, it contains the >>> correct "Content-Encoding: gzip" header, but cURL doesn't decompress it. >>> >>> Cheers, >>> Attila >>> >> -- 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 https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/11ac4859-c949-497e-bb2c-6bd1d7e18ee1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
