Settings on N7 Docs

Cookie conditions

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

This page will show you steps to configure cookie based condition. These then can be used at multiple places such as rewrite/caching/blocking rules.

Typical use-case is, you would disable cache for pages when opened in preview mode.
Here, we can achieve it by disabling caching when we have Shopify’s ‘preview_theme’ cookie is present.

Note: For demo purpose, we will be using www.nviztest.com domain as an example.
Here, we will be using preview_theme cookie. You can use any relevant cookie

Country conditions

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

This page will show you steps to configure conditions based on country from where request is originated These then can be used at multiple places such as rewrite/caching/blocking rules.

Typical use-case is, you would want to set country based redirections.

Note: For demo purpose, we will be using www.nviztest.com domain as an example. Here, we will be redirecting all requests from US to /us/.*

Prerequisite#

You must have a domain configured on Nitrogen.

Steps#

Click on Settings menu, and open Country Conditions tab.

Header conditions

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

This page will show you steps to configure header based condition. These then can be used at multiple places such as rewrite/caching/blocking rules.

Typical use-case is, you would want to pass all requests from bots to https://prerender.io/ .
Here, we can achieve it by identifying all Bot requests by value of user-agent request header.

Note: Header conditions will work only on request-headers.
For demo purpose, we will be using www.nviztest.com domain as an example. Here, we will only be using googlebot and bingbot user-agent for simplicity.

IP Addresses

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

This page will show you steps to configure conditions based on request IP. These then can be used at multiple places such as rewrite/caching/blocking rules.

Typical use-case is, you would want to block the IPs you found making malicious requests to your site.

Note: For demo purpose, we will be using www.nviztest.com domain as an example. Here, we will be blocking all requests from a blacklisted IP.

Prerequisite#

You must have a domain configured on Nitrogen.

Steps#

Click on Settings menu, and open IP Addresses tab.

HTTP methods

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

Here, you will find steps to configure conditions based on request method. These then can be used at multiple places such as rewrite/caching/blocking rules.

Typical use-case is, you would want to block TRACE, PATCH, CONNECT methods for security purpose.

Note: For demo purpose, we will be using www.nviztest.com domain as an example. Here, we will be creating method-group of TRACE, PATCH, CONNECT methods to block them.

Prerequisite#

You must have a domain configured on Nitrogen.

Steps#

Click on Settings menu, and open HTTP Methods tab.

Query params

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

This page will show you steps to configure query-parameter based condition. These then can be used at multiple places such as rewrite/caching/blocking rules.

Typical use-case is, you would want to cache and serve-from cache while ignoring the marketing/tracking query parameters (e.g. utm_*, fbclid, gclid etc.). Which will also create less cache-variations, and improve the cache-HIT percentage.

Note: For demo purpose, we will be using www.nviztest.com domain as an example. Here, we will create a query-param condition with regex pattern (utm_|fbclid|gclid) to be used to ignore them while caching/serving-from-cache.

URL patterns

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

This page will show you steps to configure request patterns. These then can be used at multiple places such as rewrite/caching/blocking rules.

Typical use-case is, you would want to proxy a set of URLs to a certain endpoint, and then set caching specific to it.
e.g. You can proxy image requests to your static domain, and set 90 days caching for them. (This way also helps avoiding extra OPTIONS calls made by browser for the request being for other domain)

Note: For demo purpose, we will be using www.nviztest.com domain as an example.
Here, we will be defining a URL pattern for relative requests of global-uploads.webflow.com domain - to proxy them to that domain itself.