I would like these vars to behave like the HTTPS var does. There are two places where these are made available: 1. ssl_engine_kernel: set in r->subprocess_env to "on" for https connections, otherwise left out 2. in util_expr_eval: as evaluation during config/htaccess expressions
HTTP2 has been implemented as in 1, I think. Part 2 is still missing. I put exported functions into mod_http2.h and added it to the include path just like mod_ssl does. If someone wants to add the util_expr_eval part, feel free. Currently busy with bugs... :( Stefan > Am 16.12.2015 um 19:39 schrieb William A Rowe Jr <[email protected]>: > > On Wed, Dec 16, 2015 at 5:40 AM, Stefan Eissing > <[email protected]> wrote: > > Subprocesses get their environment via r->subprocess_env, filled via the > "fixups" hook. This is the usual way how we involve modules in request > processing. But, as I read it, subprocess_env gets filled with all variables > for every request, even though they maybe never read? Hmm, probably a little > late to do anything about that without code breakage. > > Not 'all', that's what > https://httpd.apache.org/docs/current/mod/mod_ssl.html#ssloptions > overrides. While the 'classic' http variables are a pretty short list, > mod_ssl is > capable of creating a very large list of variables, interesting to only a few > cases. > > HTTPS=on|off is always there, and HTTP2=on|off would be similarly helpful and > very low impact.
