Miscellaneous on N7 Docs

Cache-MISS scenarios

Mon, 01 Jan 0001 00:00:00 +0000

Refer this page to know the reasons - when the origin server can get user requests even when caching is enabled, or when CDN can serve old content.

Prerequisite#

You must have caching enabled on domain.

Details#

The content you are accessing is typically served from the regional CDN Point of Presence (PoP) closest to you. However, the requested content may not be available in the cache for the following reasons:

Steps to test the website on Nitrogen without pointing the CNAME to Nitrogen

Mon, 01 Jan 0001 00:00:00 +0000

You can validate your website on Nitrogen by changing the host file entry; with which the traffic from your laptop will flow through the Nitrogen platform, while the rest of the world will continue to use the current live site.

Prerequisite#

You must have an account on Nitrogen
You must have some domain registered on Nitrogen.

Steps#

Please follow the steps shown in this link to do it as per the type of your system.

User request flow through N7 to Origin

Mon, 01 Jan 0001 00:00:00 +0000

This diagram shows the flow of user requests through N7 to origin servers

Prerequisite#

You must have domain configured on Nitrogen.

Details#

Here, when the request is made from user device, the DNS resolves it to Nitrogen.
If the response for this request is cached at Nitrogen CDN (at the CDN PoP near to user), it is returned back to user from there itself.
Else, the request is proxied to Origin. The response is then optimized by the respective modules if enabled e.g. images by AIO, videos by AVO.
(If WAF is opted, the request is terminated their itself if deemed malicious by it.)

N7 Support Severity Prioritization Matrix and Response TAT

Mon, 01 Jan 0001 00:00:00 +0000

For any technical issues/support, please send mail to support@n7.io
The Nitrogen care team continuously monitors your website for any issues, and sends alerts for any exceptional scenario observed.
Please mark e-mails from support@n7.io as not junk, and add the address to the safe-senders list.

Prerequisite#

You must have an account on Nitrogen

Details#

Whitelisting Nitrogen CDN Requests

Mon, 01 Jan 0001 00:00:00 +0000

To ensure your servers accept traffic from Nitrogen, you must whitelist our requests. We strongly recommend whitelisting by request header, as it provides a more secure and flexible setup.
For maximum security, you should configure your servers to allow traffic only from Nitrogen.

Whitelist by Request Header (Recommended)#

Configure your firewall or load balancer to allow incoming requests that contain one of the following HTTP headers.

Security Rate-Limit scenarios

Mon, 01 Jan 0001 00:00:00 +0000

The following scenarios describe how rate limits are enforced for incoming requests.

Prerequisite#

The Security module must be opted in and enabled for your domain.

Details#

They illustrate system behavior when a ban is not enabled (soft limit) versus when a ban is triggered (hard limit).

Scenario 1: Soft Rate Limit (No Ban)#

Policy Example: Limit of X requests per Y minutes per IP
Behavior:
1. Requests are tracked in a rolling time window (e.g., 60 minutes).
2. Up to X requests from a single IP are allowed during the window.
3. Any request exceeding the limit results in a 429 Too Many Requests response.
4. No ban is imposed — the IP is not blocked.
5. As older requests fall out of the time window, new requests are allowed again.
Flow Example:
1. Time 00:00 – 1st request ➜ Allowed
2. Time 00:45 – Xth request ➜ Allowed
3. Time 00:46 – X+1th request ➜ 429
4. Time 01:01 – Oldest request expires ➜ 1 new request allowed

Scenario 2: Hard Rate Limit (with Ban)#

Policy Example: Limit of X requests per Y minutes per IP ➜ Temporary ban (e.g., 15 minutes) if exceeded

Steps to use WPT to analyze the site performance

Mon, 01 Jan 0001 00:00:00 +0000

Nitrogen recommends using https://www.webpagetest.org/ (WPT for short) for measuring and comparing the performance of any website.
Because it’s easy to use, and has variety of options available like :
e.g. test location, connection speed, browser to be used, test device, DNS overriding ability, filmstrip of page load, CWV data, test comparisons, and many more things.

Prerequisite#

If you are analyzing performance through Nitrogen :

You must have an account on Nitrogen