Create a new zone
Like all CDNs, NuevoCloud is essentially a reverse proxy service. It accepts and responds to requests from the internet (over HTTP or HTTPS) for your domain.
If NuevoCloud has cached the data for the request, it will respond to the request itself. If it has not cached the data, it will proxy the request to your
server (called the origin server
). Once your server has responded to the request, NuevoCloud will send that response back to the client.
To configure a new zone, you'll need a few things:
- The domain name of your website (optional)
- IP address or URL of your origin server
In this section, you'll tell NuevoCloud how to respond to requests from the internet. The form will change depending on how you answer the questions,
so you may not see all of the options listed below.
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
would both be valid entries.
If you do not have a domain name, you'll be able to choose a nuevocloudcdn.com subdomain.
If your domain name is www.example.com
, the apex of your domain would be example.com
. In other words, selecting yes for this question would
tell NuevoCloud to redirect example.com
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
certificate should be valid for both your domain and the apex (www.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
In this section, you'll tell NuevoCloud how to contact your origin server.
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
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
be considered to be requests for http://www.example.com/resource
Test your new zone
After creating your new zone, you can now test NuevoCloud to ensure requests are being sent to your origin server correctly.
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.
Caching behavior should be tested to ensure dynamic content is detected as dynamic and that static resources are cached. This can be done by viewing the headers for a
resource on your CDN URL and examining the X-Cache header in the response.
Now that you've configued and tested your new zone, it's now ready to be used by visitors.
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.
If your domain name has a subdomain (for example, www in www.example.com):
Locate the CNAME records for your domain name, and add a CNAME record.
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.
|Your subdomainExample: www||3600||CNAME||Your NuevoCloud CDN URLExample: cdn.nuevocloudcdn.com|
- Apex (aka root) CNAME Record
Verify that your DNS provider supports Apex CNAME records. DNS providers use various names for this type of record including ALIAS, ANAME, CNAME Flattening, and Root CNAME.
Follow your DNS providers instructions for creating this type of record and use the following values:
|60||Your NuevoCloud CDN URLExample: cdn.nuevocloudcdn.com|
Getting visitor IPs
Since NuevoCloud acts as a reverse proxy, connections to your server will come from one of NuevoCloud's edge servers. When a request passes through NuevoCloud,
the IP address of the client is added to the X-Forwarded-For header. If there is not an existing X-Forwarded-For header in the request, NuevoCloud will add it:
where 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|
Automatic gzipping: extensions and file types
NuevoCloud will automatically gzip content if 1) the client making the request supports gzip; and 2) the content has the following content-type or the filename ends with one of the following extensions:
NuevoCloud also requests gzip when making requests to your origin server. Enabling gzip on your origin server will save bandwidth transferring data to NuevoCloud.
Request and response limits
NuevoCloud places the following limits on requests and responses. An error page will be displayed if these limits are exceeded.
Exceeding these limits will result in a 413 Request Entity Too Large
- Maximum POST body: 100 MiB
Exceeding these limits will result in a 502 Bad Gateway
- Maximum header size: 128 KiB
- Maximum body: 100 MiB