@@ -1267,16 +1267,16 @@ Http header verification against the tracker's ``web``
12671267setting in the ``[tracker]`` section of config.ini for the
12681268following headers:
12691269
1270- 1. Analyze the ``Referer`` HTTP header to make sure it
1271- includes the web setting.
1272- 2. Analyze the ``Origin`` HTTP header to make sure the
1273- schema://host matches the web setting.
1274- 3. Analyze the ``X-Forwarded-Host`` header set by a proxy
1275- running in front of roundup to make sure it agrees with
1276- the host part of the web setting.
1277- 4. Analyze the ``Host`` header to make sure it agrees with
1278- the host part of the web setting. This is not done if
1279- ``X-Forwarded-Host`` is set.
1270+ 1. Analyze the ``Referer`` HTTP header to make sure it
1271+ includes the web setting.
1272+ 2. Analyze the ``Origin`` HTTP header to make sure the
1273+ schema://host matches the web setting.
1274+ 3. Analyze the ``X-Forwarded-Host`` header set by a proxy
1275+ running in front of roundup to make sure it agrees with
1276+ the host part of the web setting.
1277+ 4. Analyze the ``Host`` header to make sure it agrees with
1278+ the host part of the web setting. This is not done if
1279+ ``X-Forwarded-Host`` is set.
12801280
12811281By default roundup 1.6 does not require any specific header
12821282to be present. However at least one of the headers above
@@ -1580,7 +1580,7 @@ To add this to your own tracker, add the following code (prefixed with
15801580a +) after the entry box for the new keyword in html/keyword.item.html:
15811581
15821582.. code::
1583- :class: big-code
1583+ :class: big-code
15841584
15851585 <tr>
15861586 <th i18n:translate="">Keyword</th>
0 commit comments