Re: [users@httpd] mod_lua and subprocess_env

2018-05-07 Thread Andrei Ivanov
m> > Date: Tue, Oct 3, 2017 at 1:44 AM > Subject: Re: [users@httpd] mod_lua and subprocess_env > To: us...@httpd.apache.org > > > Hi Andrei, > > Committed to trunk (http://svn.apache.org/r1810605), should have a better > visibility (and review) now. > > Regards, &

Fwd: [users@httpd] mod_lua and subprocess_env

2018-04-27 Thread Andrei Ivanov
. Thank you -- Forwarded message -- From: Yann Ylavic <ylavic@gmail.com> Date: Tue, Oct 3, 2017 at 1:44 AM Subject: Re: [users@httpd] mod_lua and subprocess_env To: us...@httpd.apache.org Hi Andrei, Committed to trunk (http://svn.apache.org/r1810605), should have a

Re: Expr's lists evaluated in a string context (was: [users@httpd] mod_lua and subprocess_env)

2017-02-23 Thread Jim Jagielski
Would it be possible that people are using it that way for exactly that purpose? I am wondering about this causing some regression for external users. > On Feb 22, 2017, at 10:51 AM, Yann Ylavic wrote: > >> On Tue, Feb 21, 2017 at 6:32 PM, Yann Ylavic

Re: Expr's lists evaluated in a string context (was: [users@httpd] mod_lua and subprocess_env)

2017-02-22 Thread Eric Covener
On Wed, Feb 22, 2017 at 10:51 AM, Yann Ylavic wrote: > > For example, the attached patch uses the seprator ", " (quite HTTP > field inspired), but it could be a json string or whatever... > We could also have an explicit tostring/tojson() function which would > stringify

Expr's lists evaluated in a string context (was: [users@httpd] mod_lua and subprocess_env)

2017-02-22 Thread Yann Ylavic
> On Tue, Feb 21, 2017 at 6:32 PM, Yann Ylavic wrote: >> >> Header set Client-SAN "expr=%{PeerExtList:2.5.29.17}" This currently fails because list functions are not recognized in a string context. For now, lists can be either expressed with the syntax "{ , , ... }", with