Google Edge Cache not works for my custom domain by HTTPS in Google App Engine application

[Andrii Chyzh]

In Google App Engine application I uses next cache headers:

 - cache-control: "public, max-age=90"

 - pragma: "Public"

When I doing request by HTTP all works great and with caching:

 - Response time: 33 ms

 - New lifetime cache header in response (Age: 24)

When I doing request by HTTPS Edge Cache does't works:

 - Response time: 466 ms

 - No any lifetime cache headers in response

How can I enable the cache for HTTPS? 

Is there a problem with the settings?

[Kenworth (Google Cloud Platform)]

The response will not be cached if any of the following are true:

1- It has a Set-Cookie header

2- Its body exceeds 10 MB

3- It has a "Vary" header with a value other than "Accept", "Accept-Encoding", or "Origin"

4- It has a "Cache-Control: no-store", "no-cache", or "private directive".

5- The corresponding request had a "Cache-Control: no-store" directive.

There are a variety of rules discussed in this article about Caching that will determine if your request will be cacheable or not. You can consult it to see what applies to your specific scenario. If you have satisfied the above and still cache is not returned on your apps' HTTPS response, I highly recommend reporting the issue on our Public Issue Tracker so proper attention can be given to it.

[Andrii Chyzh]

Hi Kenworth,

Thank you for answer!

I checked all these conditions many times and I not fixed this problem yet.

http://project-id.appspot.com - works fine

https://project-id.appspot.com - works fine

http://custom-domain.com - works fine

https://custom-domain.com - not caching

I created issue https://issuetracker.google.com/issues/65051112

Thank you!

суббота, 26 августа 2017 г., 0:28:52 UTC+3 пользователь Kenworth (Google Cloud Platform) написал:

[Kenworth (Google Cloud Platform)]

Thank you for reporting the issue. I recommend all replies and posts be directed towards that forum until a resolution is reached. 

[Andrii Chyzh]

Hi!

I already got an answer from premium support team: 
 - Node.js app uses new flexible env, Python app uses standard env. 
 - HTTPS caching with custom domain works only in old standard env.

Thank you for you time!

среда, 30 августа 2017 г., 1:21:13 UTC+3 пользователь Kenworth (Google Cloud Platform) написал: