To piggy back onto this question, what is the best way to do this such that
the values of the variables are different for every virtual host? In our
model, all virtual hosts shared the same interpreter pool but we need to
have different configuration variables on a per virtualhost basis.
Currently,
Nice, perfect, just tested, working perfectly !
Thank you very much Adam !
Ben
On 19 Oct 2017 18:39, Adam Prime wrote:
If it doesn't need to change then you should be able to set it in
PerlPostConfigRequire code, and it will then be available to all children
in copy on write memory (ie any
On 19.10.2017 12:48, Ken Peng wrote:
Hi,
for a common object on server, for example, http://a.com/b.jpg, when it can be
accessed by
client, I want to apply some access control on it, for example, the IP based AC
rules. How
will mod_perl handler deal with this? thanks.
If you do the authenti
If it doesn't need to change then you should be able to set it in
PerlPostConfigRequire code, and it will then be available to all
children in copy on write memory (ie any change will only affect the
process that changed it.)
https://perl.apache.org/docs/2.0/user/handlers/server.html#Startup_F
Hi,
I'm trying to share a var between the different processes of my prefork
Apache.
I then tried the following idea :
$r->server()->dir_config('var','val');
Unfortunately, $r->server()->dir_config('var') is not shared among the
processes.
I would have thought config was stored at the very f
With a PerlAccessHandler, see:
https://perl.apache.org/docs/2.0/user/handlers/http.html#PerlAccessHandler
Adam
On 17-10-19 06:48 AM, Ken Peng wrote:
Hi,
for a common object on server, for example, http://a.com/b.jpg, when it
can be accessed by client, I want to apply some access control on i
Hi,
for a common object on server, for example, http://a.com/b.jpg, when it can be
accessed by client, I want to apply some access control on it, for example, the
IP based AC rules. How will mod_perl handler deal with this? thanks.
Regards,
Ken Peng
