Feature #1475
closedadd url.redirect-found option to send status code 302 in the redirect module
Description
Adding new ticket, since my last ticket was SPAMMED, python errors print all over when trying to fix. Previous ticket #1446
I posted modified source to mod_redirect.c. The new feature will allow those to use the redirect functionality without having to modify the code.
You should be able to do a diff against the version of mod_redirect.c in the repository for version 1.4.18.
Thanks, Angelo Mandato
-- angelo
Files
Updated by stbuehler about 16 years ago
I will not try to get a diff out of your code, so either someone else does this or you.
Updated by Anonymous about 16 years ago
Attached is a diff of the code based on the lighttpd-1.4.x branch.
-- angelo
Updated by stbuehler about 16 years ago
Ok: What happens if you have both url.redirect and url.redirect-found in one block? Yes, only url.redirect is applied.
And perhaps the other possible redirect codes should be included, too:
- 301: Moved Permanently, as default
- 302: Found (i think this is option is somewhat "deprecated" by 303/307)
- 303: See Other
- 307: Temporary Redirect
Updated by hoffie about 16 years ago
Just on a sidenode, there is already url.redirect-code in 1.5 (see r1580).
Updated by Jochem over 12 years ago
Since 1.5 doesn't seem to be in a hurry, is there any chance the url.redirect-code setting will join the 1.4.x tree?
Updated by gstrauss almost 8 years ago
- Description updated (diff)
- Status changed from New to Fixed
- Assignee deleted (
jan) - Target version changed from 1.5.0 to 1.4.x
Updated by gstrauss almost 8 years ago
- Related to Feature #2247: Adding url.redirect-code to 1.4 added
Updated by stbuehler almost 8 years ago
- Status changed from Fixed to Duplicate
- Target version deleted (
1.4.x)
Also available in: Atom