Correct README to indicate that redirects are not done using regular expressions but literal path matches.
This commit is contained in:
parent
1794ff643b
commit
35f58f50e7
11
README.md
11
README.md
|
@ -206,11 +206,12 @@ directory listing:
|
||||||
|
|
||||||
### Redirects
|
### Redirects
|
||||||
|
|
||||||
* `TempRedirects`: In this section of the config file, keys are path
|
* `TempRedirects`: In this section of the config file, keys and values
|
||||||
regexs and values are strings. If the path component of a received
|
are both path strings. If the path component of a received request
|
||||||
request matches one of the regexs, Molly Brown will serve a redirect
|
matches one of the keys, Molly Brown will serve a redirect to the
|
||||||
to a modified URL using the value string as a path, using status
|
corresponding value, using status code 30. Note that currently
|
||||||
code 30.
|
redirects cannot be specified using regular exressions, only literal
|
||||||
|
path strings.
|
||||||
* `PermRedirects`: As per `TempRedirects` above, but Molly Brown will
|
* `PermRedirects`: As per `TempRedirects` above, but Molly Brown will
|
||||||
use the 31 status code instead of 30.
|
use the 31 status code instead of 30.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue