| commit | 5e9edce0f009bb92ac746052dd3f6d271a77d34b | [log] [tgz] |
|---|---|---|
| author | Willy Tarreau <w@1wt.eu> | Mon Apr 28 11:13:33 2014 +0200 |
| committer | Willy Tarreau <w@1wt.eu> | Mon Apr 28 17:25:40 2014 +0200 |
| tree | 5663b22fefea90184668665cc6fd9bd64153e704 | |
| parent | cfe7fdd02d1164012cf9ff04f215a724560047d9 [diff] |
MEDIUM: http: move reqadd after execution of http_request redirect We still have a plate of spaghetti in the request processing rules. All http-request rules are executed at once, then some responses are built interlaced with other rules that used to be there in the past. Here, reqadd is executed after an http-req redirect rule is *decided*, but before it is *executed*. So let's match the doc and config checks, to put the redirect actually before the reqadd completely.