Cloud CDN

[imjasonh]

Might be as simple as adding Cache-Control: max-age=0 on pong responses? The backend-service is already configured with --enable-cdn

• https://cloud.google.com/cdn/docs/

[elithrar]

You can also use gcloud beta compute backend-service update $NAME --cache-mode=FORCE_CACHE_ALL to forcibly cache the responses (as of gcloud SDK 309.0.x).

[imjasonh]

You can also use gcloud beta compute backend-service update $NAME --cache-mode=FORCE_CACHE_ALL to forcibly cache the responses (as of gcloud SDK 309.0.x).

Is that going to force the browser to cache the response and result in vacuously fast response times after the first one?

[elithrar]

Only our side - it is effectively s-maxage. You can use --client-ttl=0 to force revalidation on the client or --custom-response-header=‘Cache-Control: no-cache’ to prevent browser caching entirely.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching#Controlling_caching

The new gcloud should roll out tomorrow/this week.

On Tue, Sep 8, 2020 at 5:28 PM Jason Hall [email protected] wrote:

You can also use gcloud beta compute backend-service update $NAME --cache-mode=FORCE_CACHE_ALL to forcibly cache the responses (as of gcloud SDK 309.0.x).

Is that going to force the browser to cache the response and result in vacuously fast response times after the first one?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ImJasonH/gcping/issues/1#issuecomment-689218061, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAEQ4F5LIAMDD23XXVOQYDSE3D3NANCNFSM4DDGV7MA .