Skip to content

CDNetworks Documentation

Creating a Property permalink

To create a property, complete the Create a Property form with required information. After creating a property, save and validate the property before you deploy and test it.

Getting Started permalink

  1. In the left pane, click Edge Configurations.
  2. At the top right of the Properties page, click the Create Property button.

create property

  1. Complete the fields in the Create a Property form. Required fields are denoted by an asterisk (*).

edit property

Property NameEnter a name that helps you identify this property.
DescriptionAdd a description to associate with this property.
Configuration VersionRead-only field that shows the version number of this property. By default, your first property configuration is Version 1.
DescriptionAdd a description for this first property version.
HostnamesEnter one or more hostnames to be accelerated and which your end users will access.
OriginsOrigins are your servers that CDN360 accesses to fetch your content. You can specify more than one server. Click the Add New link and then see Adding or Editing Origins in a Property.
Edge LogicWrite NGINX configuration code to specify how you want CDN360 to deliver content to your visitors. You can click the Wizard button to bootstrap this configuration using the Cache Settings dialog box. For more information, refer to CDNetworks' Edge Logic documentation, which includes a description of supported directives.
TLS SettingsSelect the TLS client certificate settings for your property.
Real Time LoggingIf this advanced feature was enabled for you, complete the real-time logging parameters. If you require this feature, contact CDNetworks.
Advanced SettingsUse advanced settings to specify cache sharing, China ICP Beian, and a load balancer hash key.
  1. To include a baseline configuration with the Edge Logic for the property, click the gear icon at the bottom left of the Edge Logic field. When the popup appears, enter the baseline configuration. When you finish, click the Save button to save the baseline configuration to the database.

Note: If you add a baseline configuration, the wizard appends its configuration after that of the baseline configuration. When you save the baseline configuration, it will not be used to initialize the Edge Logic until you create another property. To use the baseline configuration with the current property you are adding or editing, reload the page; doing so, however, may cause you to lose other changes you made.

  1. To save the property, click the Save button. Several basic syntax checks are performed. If errors are found, you are prompted to fix them before the property is saved. Any property version will have to be "validated" before it can be deployed to staging or production. You can click the Save & Validate button to start the validation process. When the Confirmation pop-up appears, click OK. The validation process usually takes less than a minute. You can either wait for it to finish or close the progress dialog box to perform other tasks while validation continues in the background. You can click Tasks in the left pane to check the validation results. If there is a failure, perform the instructions in the error message to fix it.

  2. If the property is validated successfully, you can deploy it to the staging or production environment. By default, trial users will have access to the staging environment only. Please contact the support team to enable access to the production environment.

Edge Logic Wizard permalink

This wizard can be used to create an initial version of the Edge Logic. It supports some of the most basic cache configurations. You can modify the generated Edge Logic code to add complicated behaviors to suit your requirements. You can also set cache behavior for multiple locations.

Edge Logic Wizard

TLS Settings permalink

This section allows you to enable HTTPS for this property by attaching a TLS certificate to it. If both RSA and ECC algorithms need to be supported, add a second certificate with an algorithm different from the first certificate. This section includes an option to downgrade the protocol from HTTPS to HTTP when accessing the origin, although doing so may expose you to security risks. This section also allows you to enable Online Certificate Status Protocol (OCSP) stapling to check the revocation status of digital certificates (refer to The remaining settings are intuitive. Specify the TLS ciphers in the format described in the OpenSSL documentation.

Note: If you enter multiple cipher suites in the TLS Ciphers field, separate them with colons.

TLS Settings

Real-Time Log permalink

If you signed an agreement with CDNetworks for accessing the real-time log, use the Real-Time Log section to "stream" an access log in real time to your designated HTTP or HTTPS endpoint. You can specify the format of each log entry using NGINX variables. If you use JSON format for the log, select JSON to escape special characters in the variable values. You can also specify a sample rate to reduce the number of log entries. Use request headers to pass additional information to the receiving endpoint.

Real-Time Log

Advanced Settings permalink

Cache Key Hostname: By default, the Host header value in the client request is used in the cache key. If this property contains multiple service hostnames, the contents of different hostnames will be cached separately. If you want all hostnames to share one cached copy, specify a fixed "Cache Key Hostname" to override the default behavior.

Has ICP Beian: If this property must be served from servers in mainland China, make sure all hostnames have Beian on file with the Chinese government. You can then contact CDNetworks to enable this function for you. Once enabled, change the Has ICP Beian setting to Yes.

Note: You can set Has ICP Beian to Yes without contacting CDNetworks; however, the functionality WILL NOT be enabled until you request activation from CDNetworks.

Load Balancer Hash Key: CDN360 uses multiple tiers of load balancing to distribute client requests to different servers, with consistent hashing used in many of these places. By default, the URL is used as the hash key, which should be satisfactory in most cases. However, you can define additional variables to be added to the hash key to distribute the requests more evenly. One typical use case is when all requests carry the same URL, but use a particular header field to indicate different resources. In general, the variable(s) specified here should be a subset of the variables you enter into the cache key. Only the following variables are supported: $http_*, $cookie_*, $arg_*.

Certificate Renew Automation: By default, CDN360 takes control of the contents under the /.well-known/{acme-challenge, pki-validation} directories to support certificate auto-renew for properties. If you need to manage these two directories by yourself on the origin (for example, to implement your own certificate auto-renew mechanism), you can use this configuration option to disable the default behavior.

  • If Support is selected, CDN360 takes control of the two "special" directories to support auto-renewing of the property's certificate. This is the default setting.
  • If Disable is selected, CDN360 releases control of these special directories to the origin.

HTTP/2: Use the radio buttons to enable or disable the HTTP/2 protocol. HTTP/2 is enabled by default. If disabled, HTTP/1.1 is used.

Property Advanced Settings