1

In the docs, I see that "cdn_cache_id" can be used as a header value, but I received an "Invalid header value" error when using it. I tried to apply it using Cloud Shell and UI, but it's the same. Can anyone confirm what really happened here?

cdn_cache_id error

Frans Allen
  • 36
  • 4
  • 2
    This appears to be a bug: the correct value is indeed `{cdn_cache_id}`, but the UI (if you Ctrl/Cmd+Space) will show `{cache_id}`. I've filed a bug to have this fixed ASAP. In the meantime, you can use gcloud via Cloud Shell, which works: `➜ gcloud beta compute backend-services update serverless-backend --custom-response-header='X-Frame-Options: DENY' --custom-response-header='Cache-Status: {cdn_cache_status}' --custom-response-header='Cache-ID: {cdn_cache_id}'` – elithrar Oct 28 '20 at 20:31
  • Ok, I'll go with Cloud Shell from here. Thanks @elithrar. – Frans Allen Oct 29 '20 at 04:39
  • This is now fixed and live. – elithrar Nov 05 '20 at 18:17

1 Answers1

1

As it was mentioned by @elithrar at the comment section, this issue was reported and Google Engineers are aware of this issue.

You can keep track of the issue report status by following this thread at Google Public Issue Tracker.

EDIT This is now fixed, and the input field validation now (correctly) accepts {cdn_cache_id} in Console:

CDN

Serhii Rohoza
  • 4,287
  • 2
  • 16
  • 29