On Thursday 22 December 2005 22:18, Chris Darroch wrote: > Well, this may be a sore point, but I'll tackle it anyway, > so apologies in advance. The fact that environment variables > created with SetEnv are applied during the fixups phase, > while SetEnvIf creates its variables during the post_read_request > and header_parser phases, does make my life a little more > painful. > > This has been raised in various bug reports, including #36908 > and #35611. These are marked "won't fix", with the explanation > that SetEnv is intended for use by content generators like CGI > scripts.
This looks a lot like the situation with mod_headers, that we solved some time ago by introducing the "early" keyword. AFAICS the same solution would work for mod_env. The number of bug reports you cite evidences a demand for it. That would be a very quick and easy solution. The solution you propose in your followup seems rather close to folding mod_env into mod_setenvif in a manner designed to be internally consistent. That too makes sense to me, but would want a little more thought. Anyone else? -- Nick Kew
