From: "Brian Pane" <[EMAIL PROTECTED]> Sent: Thursday, January 10, 2002 12:50 AM
> William A. Rowe, Jr. wrote: > > >I'm really thinking that SetEnvIf can be broken down into; > > > > request vars > > input vars > > output vars > > > >And these could be tested on at the appropriate points [output vars don't > >get tested until the -end- of fixups, for example.] > > > >This would make the entire EnvIf schema faster, even if that request vars > >subset needs to be tested more than once. Input vars don't change, so they > >only need testing once after parsing, output vars aren't complete till the > >fat lady sings, so to speak. > > That makes sense, except for one part that I don't understand: what are the > input vars, if they're not the same as the request vars? Input vars are as-given by the client. Request vars [as I'm defining them] are those we munge on the way to serving the request. So they change as the modules get their fingers in there :)
