okey, here's anpther take on the %2f thing. as a reminder, we currently reject any reques that includes an encoded slash in the pat with a 404. this breaks environments which need to use %2f in the path info. the issue has to do, in part, with decoding the %2fs into slashes, and possibly having to re-encode them again.
i've been fighting with saving %2f state and restoring it for a long time, but to no definitely acceptable conclusion. but last week a possible alternative came to mind: if the AllowEncodedSlashes directive is set to 'on', unencode everything *except* %2f. then let it go through the normal processing. if %2f is part of the path, the request will fail with a 404 anyway when the document isn't found; if the %2f is strictly in the path-info, it won't intefere with document location and will be available to the resource as expected. i have a patch for this against 2.1 that i'd like to send, but i won't bother if people are going to veto all over it without even looking at it.
