Troubleshoot common issues

Available in Classic and VPC

You might run into the following problems when using Global CDN. Find out causes and possible solutions.

Troubleshoot HTTPS protocol unavailable issues

I need to use HTTPS, but only the HTTP protocol is supported when I use my domain.
I want to use HTTPS while using my own domain.

Cause

When you use your own domain for the service domain, Global CDN does not support HTTPS protocols.

Solution

When you need to use your own domain, use Global Edge.

Troubleshoot unspecific image calls unavailable issues

An unspecific image is not being called.

Cause

• Responses may not be performed properly due to the load on the origin.
• If you perform all Purges, communication between the origin and CDN may not function properly while the entire content is newly cached.

Solution

Check whether requests can be processed normally in the origin.

If you need an analysis of the CDN service domain's requests, you can check it by enabling Access Log. To enable Access Log, follow these steps:

1. From the NAVER Cloud Platform console, navigate to > Services > Content Delivery > Global CDN.
2. Click the [Change settings] button.
3. Set Access Log to Enable.

Troubleshoot Cache Poisoning occurrence issues

Cache Poisoning issues occur.

Cause

Global CDN providers have changed some settings since June 1, 2023. So, unexpected Cache Poisoning issues may occur during communication with the origin due to the allowance action of HTTP Header (Example: Custom Header) including non-standard strings.
Example: " \ host: bad-hostname.com"

Non-standard (non-RFC) Header strings are as follows. For more information, see RFC 9110.

"(" or ")" or "<" or ">" or "@" or "," or ";" or ":" or "" or "<" or ">" or "/" or "[" or "]" or "?" or "=" or "{" or "}"

Solution

Global CDN providers perform the task of enhancing Header Parsing as default in progress. If you use non-standard headers, contact Customer Support.