Probably many existing users won't like seeing the AUTHORIZE_ headers from the other apache auth modules suddenly appearing in the child process' environment, so it would probably be best to put that behind a flag...
No issues have been noted with the last set of changes since v3.3.3, so after the change above, it's probably safe to release v.3.3.4...
Probably many existing users won't like seeing the AUTHORIZE_ headers from the other apache auth modules suddenly appearing in the child process' environment, so it would probably be best to put that behind a flag...
No issues have been noted with the last set of changes since v3.3.3, so after the change above, it's probably safe to release v.3.3.4...