I cannot reproduce this behavior on my side. All of my own applications serve responses with either the *Content-Length* header or the Transfer-Encoding: chunked with and without SSL. In addition, the URL you provided also always serves responses with one of those headers. More accurately, the Google Front End has always been serving responses with said headers. I suspect the headers might be stripped elsewhere.
Could you provide a code sample of the client getting the responses? Perhaps a local library is stripping headers or performing some other changes behind the scenes. On Saturday, March 12, 2016 at 6:06:50 AM UTC-5, Linus Larsen wrote: > > Sometime yesterday (10th), our clients started to behave strage. After > some investigation it seems like Google decided to remove the Content-Length > header from the http responses. The request / response messages between > our clients are actually small protobuf encoded binary messages, using > Content-Type: application/octet-stream, and this has worked flawless uptil > now. > > Ok, we thought we just set the clients to use HTTP1.0, since > Content-Length header is mandatory in 1.0. But that didn't help we still > don't get any > Content-Length IMO this GAE behavior breaks GAE and HTTP1.0 compability. > > So, why is the Content-Length header missing? It was there before but has > been removed, why wasn't we informed? > > > > -- 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/f4481b12-5336-4fb1-a7f3-50232efc2698%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
