CDN+ Migration

Prev Next

Available in Classic and VPC

This section describes how to migrate from CDN+ to Global Edge service.
You will be guided for seamless migration with the functional comparison of Global Edge service config options based on the CDN+ service config options.

CDN+ Config options Global Edge guide
Service settings Service protocol You can apply the same settings as CDN+ by selecting Global Edge Console > Deployment settings –> Service settings –> Service protocol > HTTP, HTTPS, HTTP, and HTTPS.
Service domain You can apply the same settings as CDN+ by selecting Global Edge Console –> Service settings –> Service Domain > Use NAVER Cloud Platform domain (automatic generation), Use NAVER Cloud Platform domain (enter manually) and Use customer's domain.
AccessLog You can apply the same settings as CDN+ by selecting Global Edge Console > Deployment settings and enabling the Global Edge Logging option.
When you select a Region in the GE Global Edge Logging settings, Bucket prefix option is added, and then you can specify the path to save the Region and logs of the Object Storage where log files are to be stored.
Source settings Source location You can apply the same settings as CDN+ by selecting Global Edge Console > Source settings > Source domain > Use Object Storage and Use the External Origins.
Source path (optional) Select Global Edge Console > Source settings > Source path > enter the path in the form of "/base_directory_name/". However, you must add "/" to the name of the bottom-most directory, unlike in CDN+. (You do not add "/" to the bottom-most directory in CDN+.)
Forward Host Header You can apply the same settings as CDN+ by selecting Global Edge Console > Source settings > Forward Host Header > Incoming Host Header, Origin Hostname, and Custom.
Cache Key Hostname You can apply the same settings as CDN+ by selecting Global Edge Console > Cache settings > Cache Key Hostname > Incoming Host Header and Origin Hostname.
Gzip Compression Enabled by default in Global Edge console, this uses the Accept-Encoding header as a cache key. You cannot set the option in Global Edge Console.
Custom Header (origin request) You can apply the same settings as CDN+ by selecting Global Edge Console > Rule builder > HTTP Header Modification > Modify Origin Request Header > Action and specifying Header Name and Value.
Cache settings Caching Option You can apply the same settings as CDN+ by selecting Global Edge Console > Cache settings > Enable Default Caching option > Cache options > Prioritize Origin Cache-Control header, Cache, and Bypass Cache.
Force Revalidation of Stale Objects You can apply the same settings as CDN+ by selecting Global Edge Console > Cache settings - Enable Default Caching option > Serve Stale object > Serve stale if unable to validate and Always revalidate with origin. However, Serve stale if unable to validate and Always revalidate with origin options are not supported for bypass caches.
Cache expiry You can set this up by selecting Global Edge Console > Cache settings > Enable Default Caching option and manually entering a value in Maxage. However, this is available only when the caching option is set to Cache.
Ignore Query String You can apply the same settings as CDN+ by selecting Global Edge Console > Cache settings > Cache key Ignore Query String > Allow all and Ignore all.
Remove Vary Header You can apply the same settings as CDN+ by selecting Global Edge Console > Cache settings and disabling/enabling the Remove Vary Header option.
Large File Optimization You can apply the same settings as CDN+ by selecting Global Edge Console > Optimization and disabling/enabling the Large file transfer option.
Viewer transfer settings Gzip Compression You can apply the same settings as CDN+ by selecting Global Edge Console > Optimization and disabling/enabling the Compressed transfer option. However, the Apply the same compression settings as the source option is not supported in the Global Edge console.
Referer Domain You can apply the same settings as CDN+ by selecting Global Edge Console > Access control > Access Control > Add Referrer Header and specifying Referrer. However, you cannot set Allow when there is no referrer > Not allow for the Global Edge console.
Security Token You can set this by selecting Global Edge Console > Cache settings and enabling the Edge Auth option. - Currently, you cannot use the token key value used in CDN+ for the GE console; therefore, you need to adjust the value (through automatic generation).
Custom Header (user response) You can apply the same settings as CDN+ by selecting Global Edge Console > Rule builder > HTTP Header Modification > Modify Client Response Header > Action and specifying Header Name and Value. In GE, you can now enter Rule Name.