<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Location Table</title><link>https://sourceforge.net/p/redird/wiki/Location%2520Table/</link><description>Recent changes to Location Table</description><atom:link href="https://sourceforge.net/p/redird/wiki/Location%20Table/feed" rel="self"/><language>en</language><lastBuildDate>Mon, 22 Jan 2018 16:48:08 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/redird/wiki/Location%20Table/feed" rel="self" type="application/rss+xml"/><item><title>Location Table modified by Ray</title><link>https://sourceforge.net/p/redird/wiki/Location%2520Table/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v1
+++ v2
@@ -5,7 +5,9 @@
 If none of the above yields a valid host:port value, the default redirection (see option **-s**) is used, if configured. If it is not configured, a HTTP 404 Not Found response is sent to the client.

 The location table has a simple syntax specifying one redirection per line:
+
 `host:port LWSP+ URL `
+
 LWSP is either a space or a tab and there must be at least one. Empty lines and lines starting with a hashmark are ignored.
 **Note** the comparison is case-insensitive, but does **NOT** incorporate any DNS (or other naming services) search. Thus if you know that your servers can be referenced both by bare hostnames and FQDNs, then you MUST specify *two* redirection lines for each, e.g.

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ray</dc:creator><pubDate>Mon, 22 Jan 2018 16:48:08 -0000</pubDate><guid>https://sourceforge.net0aafabe86ba114b9f68e993a8381b28fa3ede94c</guid></item><item><title>Location Table modified by Ray</title><link>https://sourceforge.net/p/redird/wiki/Location%2520Table/</link><description>&lt;div class="markdown_content"&gt;&lt;h1 id="location-table"&gt;Location Table&lt;/h1&gt;
&lt;p&gt;The location table is a simple file of key-value pairs. The file is used to determine the target URL to which the client should be redirected. When the client specifieds the Host header within the HTTP request (which is mandatory starting HTTP/1.1 up), the value specified in the header takes precedence over the authority specified in the request URL. &lt;br/&gt;
When the Host header is missing (HTTP/1.0 and below), &lt;strong&gt;redird&lt;/strong&gt; extracts the authority part (host:port) from the request URI, adding the port 80 if omitted. &lt;br/&gt;
In any case, the resulting host:port key is sought in the location table file and if a match is found, the corresponding value of the pair is used as the base of the target URL.&lt;br/&gt;
If none of the above yields a valid host:port value, the default redirection (see option &lt;strong&gt;-s&lt;/strong&gt;) is used, if configured. If it is not configured, a HTTP 404 Not Found response is sent to the client.&lt;/p&gt;
&lt;p&gt;The location table has a simple syntax specifying one redirection per line:&lt;br/&gt;
&lt;code&gt;host:port LWSP+ URL&lt;/code&gt;&lt;br/&gt;
LWSP is either a space or a tab and there must be at least one. Empty lines and lines starting with a hashmark are ignored.&lt;br/&gt;
&lt;strong&gt;Note&lt;/strong&gt; the comparison is case-insensitive, but does &lt;strong&gt;NOT&lt;/strong&gt; incorporate any DNS (or other naming services) search. Thus if you know that your servers can be referenced both by bare hostnames and FQDNs, then you MUST specify &lt;em&gt;two&lt;/em&gt; redirection lines for each, e.g.&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;myweb.example.com:80  http://intranet.example.com/myweb
myweb:80              http://intranet.example.com/myweb
&lt;/pre&gt;&lt;/div&gt;

&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ray</dc:creator><pubDate>Mon, 22 Jan 2018 16:47:48 -0000</pubDate><guid>https://sourceforge.net6e8563e7709148bccdfbf94222666766f585b60b</guid></item></channel></rss>