To configure a new zone, you'll need a few things:
When you select yes, it will ask you for the domain name for your website. This should include the subdomain (if any). For instance, example.com or www.example.com would both be valid entries.
If you do not have a domain name, you'll be able to choose a nuevocloudcdn.com subdomain.
If you are using your own domain name, you'll be asked if you want to enable SSL for that domain. If you choose to enable it, you'll be asked for the SSL certificate that NuevoCloud should use for your domain. The Common Name for the certificate should match the domain name. If you enabled Redirect Apex, your certificate should be valid for both your domain and the apex (www.example.com and example.com).
Redirect HTTP to HTTPS
Enabling this option forces all clients to connect using SSL. Connections over HTTP will be redirected to HTTPS.
HSTS (HTTP Strict Transport Security) is a web security policy mechanism. It allows you to tell web browsers that they should always connect over HTTPS. If you enable HSTS, you'll be asked for a Max Age setting in seconds. Max Age is how long browsers should remember to only connect over HTTPS. Only enable this setting if you are sure you want to permanently enable SSL, since it cannot be disabled quickly.
Note: HSTS is only available if you have enabled Redirect HTTP to HTTPS.
Origin Server URL
This should be the URL to your origin server, including the protocol and path (if any). NuevoCloud will append the requested resource path to this URL. For example, if a visitor requests www.example.com/resource, and your Origin Server URL is https://0.0.0.0/folder, NuevoCloud will connect to https://0.0.0.0/folder/resource.
You can use a domain name in the Origin Server URL, but you must not use the domain name you entered under Website Settings.
Forward Query String
The query string is the portion of the URL after the ?. For example, in http://www.example.com/resource?q=value the query string is q=value.
If you enable this setting, NuevoCloud will consider the query string as part of the URL and will forward the query string when sending requests to your origin server.
If this is disabled, NuevoCloud will ignore the query string. Meaning http://www.example.com/resource?q=value1 and http://www.example.com/resource?q=value2 would be considered to be requests for http://www.example.com/resource.
On the dashboard for your new zone, find your CDN URL and copy&paste this URL into your browser. If everything is working correctly, you should see a response from your origin server.
If you received an error, edit your zone settings by clicking the Edit Settings button on the zone dashboard.
If you do not have a domain name, you can use your CDN URL directly. There are no changes that need to be made to your DNS settings. You're finished.
If you do have a domain, you'll need to create a couple of DNS records with your DNS provider for the domain.
|3600||CNAME||Your NuevoCloud CDN URL|
If your domain does not contain a subdomain OR you enabled Redirect Apex in the zone settings, you'll need to add an Apex CNAME record.
|60||Your NuevoCloud CDN URL|
If you need assistence optimizing your website, send us an email and one of our engineers would be happy to help.
Surrogate-Control: public, max-age=86400
Cache-Control: max-age=3600, must-revalidateOptions
|max-age||The maximum number of seconds the resource should be considered fresh.|
|s-max-age||Similar to max-age, but only applies to shared caches.|
NuevoCloud will use s-max-age (instead of max-age) if it's present.
|If any of these options are present, NuevoCloud does not cache the resource.|
Expires: Tue, 01 Jan 2030 00:00:00 GMT
These options can be combined to control both NuevoCloud's cache and the visitors browser cache separately. For example, to cache a resource at the CDN edge for 24 hours, but not in a visitor's browser cache, you could use headers similar to this:
Surrogate-Control: max-age=86400 Cache-Control: no-cache Expires: -1In this example, you can take advantage of NuevoCloud's caching, but since the resource is never cached by the browser, when you purge a file from NuevoCloud, you can be sure all of your visitors are seeing the new file.
Cache headers are one of the most useful tools at your disposal to implement your cache policy.
X-Forwarded-For: A.B.C.Dwhere A.B.C.D is the client IP address. If the header already exists, NuevoCloud will append the client IP address to the header:
X-Forwarded-For: a.a.a.a, b.b.b.b, A.B.C.D