<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Settings on N7 Docs</title><link>https://docs.n7.io/sera/settings/</link><description>Recent content in Settings on N7 Docs</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.n7.io/sera/settings/index.xml" rel="self" type="application/rss+xml"/><item><title>Header conditions</title><link>https://docs.n7.io/sera/settings/header-conditions/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.n7.io/sera/settings/header-conditions/</guid><description>&lt;p&gt;This section shows the steps to configure header based condition.
&lt;/br&gt;&lt;/br&gt;
Typical use-case is, you would want to pass all the bots requests to &lt;a href="https://sera.n7.io/" target="_blank" rel="noreferrer"&gt;sera.n7.io&lt;/a&gt;
.&lt;/br&gt;
Here, you can achieve it by providing all Bot patterns by setting the value of user-agent request header.
&lt;/br&gt;&lt;/br&gt;
&lt;em&gt;Note: Header conditions will work only on &lt;b&gt;request&lt;/b&gt;-headers.&lt;/br&gt;
For demo purpose, we will be using &lt;code&gt;example.com&lt;/code&gt; domain as an example. Here, we will only be using &lt;code&gt;googlebot&lt;/code&gt; and &lt;code&gt;bingbot&lt;/code&gt; user-agent for simplicity.&lt;/em&gt;&lt;/br&gt;&lt;/p&gt;</description></item><item><title>Query params</title><link>https://docs.n7.io/sera/settings/query-params/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.n7.io/sera/settings/query-params/</guid><description>&lt;p&gt;This page will show you steps to configure query-parameter based condition. These then can be used at Query Filters in Rules section.
&lt;/br&gt;&lt;/br&gt;
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.&lt;/br&gt;&lt;/br&gt;
*Note: For demo purpose, we will be using &lt;code&gt;example.com&lt;/code&gt; domain as an example.&lt;/br&gt;&lt;/p&gt;
&lt;h2 id="prerequisite"&gt;Prerequisite&lt;a class="heading-anchor" href="#prerequisite" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;You must have a domain configured on Nitrogen.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="steps"&gt;Steps&lt;a class="heading-anchor" href="#steps" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Click on &lt;code&gt;Settings&lt;/code&gt; menu, and open &lt;code&gt;Query Params&lt;/code&gt; tab.&lt;br/&gt;
&lt;img src="https://docs.n7.io/assets/images/Sera/settings/query/list.png" alt="Step" &gt;
&lt;/p&gt;</description></item><item><title>URL patterns</title><link>https://docs.n7.io/sera/settings/url-patterns/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.n7.io/sera/settings/url-patterns/</guid><description>&lt;p&gt;This page will show you steps to configure request patterns. These then can be used at multiple places such as rewrite/caching/blocking rules.
&lt;/br&gt;&lt;/br&gt;
Typical use-case is, you would want to proxy a set of URLs to a certain endpoint, or use in a certain condition group.&lt;br/&gt;
&lt;/br&gt;&lt;/br&gt;
*Note: For demo purpose, we will be using &lt;code&gt;example.com&lt;/code&gt; domain as an example.&lt;/br&gt;
Here, we will be defining a URL pattern for Non SERA requests patterns&lt;/br&gt;&lt;/p&gt;</description></item></channel></rss>