It's a bit problematic, since we have our own CA cert and our clients sends 
encrypted packages (besides SSL). However these headers are 
what we get using http 1.0:

localhost:~$ curl -0 -I --cacert ~/cert/rootCA/rootCA.crt 
https://outlet.epspot.com/services/secure_outlet/hello
HTTP/1.0 200 OK
Content-Type: text/plain
Date: Sat, 12 Mar 2016 14:48:56 GMT
Server: Google Frontend
Alt-Svc: quic=":443"; ma=2592000; v="31,30,29,28,27,26,25"

This is what the clients are using (http POST)

HTTP/1.0 200 OK
Content-Type: application/octet-stream
Date: Sat, 12 Mar 2016 14:26:55 GMT
Server: Google Frontend
Cache-Control: private
Alt-Svc: quic=":443"; ma=2592000; v="31,30,29,28,27,26,25"
Accept-Ranges: none
Vary: Accept-Encoding

Using HTTP1.1 we get no Content-Length as well, however Content-Length were 
present before yesterday.

/ Linus

Den lördag 12 mars 2016 kl. 15:28:12 UTC+1 skrev Nickolas Daskalou:
>
> Hi Linus,
>
> Do you have a public URL we can test?
>
> Nick
> On 12/03/2016 10:07 PM, "Linus Larsen" <[email protected] <javascript:>> 
> 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] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> 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/2d8c8dbb-8f93-4935-84ea-2bcc2f86de9f%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/2d8c8dbb-8f93-4935-84ea-2bcc2f86de9f%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/b97cc796-e248-430f-97d7-5d065a244f5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to