On 26-Nov-04, at 11:14 AM, Stas Bekman wrote:
[EMAIL PROTECTED] wrote:
[...]
More precisely, if I set (for example) the LogLevel to error, I
only get
error and more critical logs AND also notice logs (but not warn
logs).
I can reproduce that problem. I'll keep you posted when I get a chance
to
Disclaimer: the following is all to the best of my knowledge.
Take it for what it's worth.
On 8-Nov-04, at 9:27 AM, Martin Moss wrote:
so therefore I wonder if I can use this,
e.g. map my session_id to a UUID, and then when I
check the session is valid I crosscheck this, however
I'm not sure if I
On 18-Sep-04, at 8:37 AM, Stas Bekman wrote:
What about the unset via set functionality? I don't remember it
being in mp1.
I didn't actually do anything to implement that; as in mp1 (I presume)
it sets
the variable to an empty string, discarding any previous values. Unless
someone
actually
On 17-Sep-04, at 4:55 PM, Stas Bekman wrote:
Geoffrey Young wrote:
Rici Lake wrote:
[...]
As a little bonus, it adds the
directive PerlUnsetVar
hmm... I guess this would be useful. but what does it do, unset the
last
value (of multiple adds) or clear the table entry entirely? if the
latter
On 17-Sep-04, at 4:55 PM, Stas Bekman wrote:
I'd rather not add new directives, but have:
On reflection, I think I agree. It is possible to achieve virtually
the same effect with
PerlSetVar foo
So I trimmed a few lines out of the patch, ran the tests again, and
this time I will cut and paste it
On 17-Sep-04, at 7:36 PM, Stas Bekman wrote:
and if you can send the missing tests and docs that will ensure that
your patch will be committed promptly.
As I can see src/docs/2.0/user/config/config.pod's PerlSetVar entry is
completely empty :( So it needs to be ported from the mp1 docs first
Hi, Ben (and modperl folken)
I've pieced together your config file from the bit's you've sent me and
posted; I deleted the ip numbers, but here is what I think it basically
looks like:
# Doesn't work
Location /server-status
SetHandler server-status
Order deny,allow
Deny from all
On 1-Sep-04, at 3:57 AM, M.v.Buytene wrote:
Limit = {
METHODS = 'GET POST',
require = 'valid-user',
Order = 'allow,deny',
Allow = 'from all',
},
Apparently, the documentation is wrong (which is why I
ended
In the course of trying to figure out why mod_info does not reveal
directives added in PerlSections (see other email), I stumbled across
the following problem:
I created a simple seven-line .htaccess file, and did 100,000 requests
to a file in the corresponding directory with ab. All processes
While trying to debug an issue with a Perl section in mod_perl2, I
noticed that these sections are not shown in mod_info's output. I also
ran into some issues in mod_info itself.
In case these tools are useful to someone else, I have placed the new
improved mod_info.c and a patch for
10 matches
Mail list logo
