[google-appengine] Re: Content-Length response header

2016-03-25 Thread 'Nicholas (Google Cloud Support)' via Google App Engine 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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.

[google-appengine] Re: Content-Length response header

2016-03-23 Thread 'Nicholas (Google Cloud Support)' via Google App Engine 
Thanks for the additional information. I'll attempt a little further to 
reproduce the issue and reach out if I require additional information. I 
will get back to you either way within the next few days.

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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/d67ee316-3450-4b79-b321-21fe02049ec0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Content-Length response header

2016-03-21 Thread Linus Larsen 
FYI, we are using JAVA and no proxies in between. There is no problem doing 
a ordinary GET with curl or browser, the Content-Length header is there. 
I think this issue has to do with SSL. We have a custom domain, our own 
root certificate, and a dispatch.xml routing the traffic. Previous I posted 
an example
request for a "Hello World" request:

localhost:~$ curl -0 -I --cacert ~/cert/rootCA/rootCA.crt 
https://outlet.epspot.com/services/secure_outlet/hello

Obviously I cannot post our root certificate here, but it should give you 
an indication where the problem might be. As a mentioned before our real 
clients
is using POST and binary encoding, but it does't seem to matter, 
Content-Length header is missing.

/ Linus

 



Den fredag 18 mars 2016 kl. 21:35:36 UTC+1 skrev Nicholas (Google Cloud 
Support):
>
> According to this article 
> , 
> the 'Content-Length' and 'Transfer-Encoding' headers are remove from 
> responses your application may serve. Those headers are then added by the 
> Google Front End and finally, the response is served.
>
> I can't yet reproduce what you're experiencing as all GET and POST 
> requests to both my App Engine and MVM instances return 'Content-Length' 
> headers. Could you provide the following information so we could narrow our 
> testing requirements:
>
>- Request headers
>- Runtime specs (Java, Python, PHP, Go, MVM)
>- Code sample of your request handler
>- Does this occur with all your modules/versions?
>- If you deploy a 'Hello World', do you also get responses without 
>these headers?
>- Is their any proxy between the Google Front End and the client that 
>might be removing these headers?
>
> Any information you can provide to more effectively diagnose or reproduce 
> the issue would be very helpful.
>
>
> 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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/4e0ab957-efc3-442f-85e2-1cdccc1d8e4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Content-Length response header

2016-03-18 Thread 'Nicholas (Google Cloud Support)' via Google App Engine 
According to this article 
, 
the 'Content-Length' and 'Transfer-Encoding' headers are remove from 
responses your application may serve. Those headers are then added by the 
Google Front End and finally, the response is served.

I can't yet reproduce what you're experiencing as all GET and POST requests 
to both my App Engine and MVM instances return 'Content-Length' headers. 
Could you provide the following information so we could narrow our testing 
requirements:

   - Request headers
   - Runtime specs (Java, Python, PHP, Go, MVM)
   - Code sample of your request handler
   - Does this occur with all your modules/versions?
   - If you deploy a 'Hello World', do you also get responses without these 
   headers?
   - Is their any proxy between the Google Front End and the client that 
   might be removing these headers?
   
Any information you can provide to more effectively diagnose or reproduce 
the issue would be very helpful.


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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/e90cdd08-35c6-4d4b-9d25-59b5af718bed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.