From 592c13a20f5ece4a596635c75bf096ccd3dfa6b8 Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Fri, 6 Jun 2025 23:56:11 +0000
Subject:  Prepare for 0.0.7.0; add noredirect

Signed-off-by: Laurent Bercot <ska@appnovation.com>
---
 doc/tipidee.conf.html | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

(limited to 'doc/tipidee.conf.html')

diff --git a/doc/tipidee.conf.html b/doc/tipidee.conf.html
index f60fa32..a9b5063 100644
--- a/doc/tipidee.conf.html
+++ b/doc/tipidee.conf.html
@@ -847,6 +847,21 @@ requests received on port 443). But if you declare a redirection under the
 <tt>example.com</tt> domain, it will apply to requests received on <em>any</em> port. </li>
 </ul>
 
+<div id="noredirect">
+<h4> <tt>noredirect</tt> </h4>
+</div>
+
+<p>
+ <code> noredirect <em>resource</em> </code>
+</p>
+
+<ul>
+ <li> This directive prevents <em>resource</em> from being redirected. It is typically
+useful to carve exceptions to a generic redirection policy: if you have a <code>redirect</code>
+directive for directory A and a <code>noredirect</code> directive for resource B, and A is
+a prefix of B, then B will not be redirected, but everything else under A will. </li>
+</ul>
+
 <div id="custom-response">
 <h4> <tt>custom-response</tt> </h4>
 </div>
-- 
cgit v1.3.1