bin/50171: bozohttpd enhancements

[mspo%mspo.com@localhost]

>Number:         50171
>Category:       bin
>Synopsis:       bozohttpd enhancements
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 25 14:15:00 +0000 2015
>Originator:     matthew sporleder
>Release:        7
>Organization:
netbsd.org
>Environment:
NetBSD wip.pkgsrc.org 7.0_BETA NetBSD 7.0_BETA (XEN3_DOMU) #3: Thu Jun  4 19:33:17 UTC 2015  root%amdmin.netbsd.de@localhost:/home/netbsd/7/amd64/obj/sys/arch/amd64/compile/XEN3_DOMU amd64
>Description:
There are two extremely common things web servers do that bozo should also be able to do:

redirect on files

use a fall-back resource
---

Right now bz seems to support redirecting entire directories, but not individual paths (I guess you could mkdir /file.html; ln -s ..) but maybe just a simple file containing redirects .bzredirs would be easier?

a fallback resource is very very common when using a "handler' for files which do not exist. This is commonly seen in apache as:
RewriteRule ! -f
RewriteRule ! -d
RewriteRule ^ /index.php

Where index.php will then handle the request, getting the UA's given url from the environment.  This ends up looking a lot nicer than a real redirect to /index.php?url=foo or even /index.php/foo
>How-To-Repeat:

>Fix: