While the "location match / block 302 URI" mechanism works fine for
some web applications using "GET", it won't work for "POST"

Browsers do 302 redirections as GET - so POST form data is lost

Most browsers do not respect the 307 redirects to re-POST

There is no way to differntiate in the "loction match" stanza
between a POST and GET to return different codes.

My proposal is for adding a optional URI parameter to "pass"
with the same macros as for "block" that will cause httpd to (try to)
serve the actual expanded URI - this way replicating the
mod_rewrite functionality, preserving the "nice looking" URLs in
the user’s browser and getting POST to work.