Hi all,
I am trying to debug a problem with mod_dbd, and the creation of
prepared statements.
If I run the following three steps, the first adds the prepared
statement, the second obtains a handle to the dbd functions, and the
third statement retrieves the prepared statement.
For some reas
Perhaps it would make more sense to provide this as an explicit value rather
than
On vs. Off and set the default to the previous behavior. Perhaps something like:
AuthzMergeRules [AND | OR | OVERRIDE] with default being OVERRIDE (if I grok
correctly)
Meaning that any directives specified at on
Brad Nicholes wrote:
So here was the thinking behind it when AuthzMergeRules was introduced.
Maybe there is still a bug here that needs to be addressed.
http://mail-archives.apache.org/mod_mbox/httpd-dev/200607.mbox/[EMAIL PROTECTED]
http://mail-archives.apache.org/mod_mbox/httpd-dev/200607.mbo
>>> On 4/4/2008 at 11:37 AM, in message <[EMAIL PROTECTED]>, Chris
Darroch <[EMAIL PROTECTED]> wrote:
> William A. Rowe, Jr. wrote:
>
>>> I've been working with the 2.4 authn/z stuff a bit lately and
>>> what I keep tripping over is that the default authorization merge rule
>>> uses OR logic. F
Graham Leggett wrote:
A session is a simple table of key value pairs.
mod_session_dbd stores sessions within a SQL database. The session is
tracked by a cookie, very similar to a typical Tomcat session. The catch
is that you need a database beefy enough to handle the resulting load,
which m
Plüm wrote:
I am still not convinced. What makes you sure that a previous merge
did not set entry_core->r / entry_core->d. But maybe it is just my
missing experience with the config and merge system.
It is
1) the job of to do so.
2) the job of any which throws away the
results to
> -Ursprüngliche Nachricht-
> Von: Nick Kew
> Gesendet: Freitag, 4. April 2008 00:06
> An: dev@httpd.apache.org
> Betreff: Re: svn commit: r644253 - in /httpd/httpd/trunk:
> docs/manual/mod/core.xml include/ap_mmn.h include/http_core.h
> server/core.c server/request.c
>
> On Thu, 03
William A. Rowe, Jr. wrote:
I've been working with the 2.4 authn/z stuff a bit lately and
what I keep tripping over is that the default authorization merge rule
uses OR logic. For example, if I enable mod_access_compat and
put in a traditional:
I wonder if anyone would offer a fastfeather t
On Fri, 04 Apr 2008 17:03:06 +0200
Graham Leggett <[EMAIL PROTECTED]> wrote:
> It would be significantly simpler to teach Apache how to do form
> logins,
+1. It's something no doubt most of us have reinvented.
A standardised/bundled solution would be great!
> It is hoped that with a standard se
Hi all,
Despite having a very capable pluggable aaa subsystem built into httpd,
the two main mechanisms for access remain mod_auth_basic and
mod_auth_digest.
Many web applications demand more flexible or user friendly ways to log
into the server, and so every application server out there has
>>> On 4/4/2008 at 1:20 AM, in message <[EMAIL PROTECTED]>, "William
A. Rowe, Jr." <[EMAIL PROTECTED]> wrote:
> Chris Darroch wrote:
>>
>> I've been working with the 2.4 authn/z stuff a bit lately and
>> what I keep tripping over is that the default authorization merge rule
>> uses OR logic. Fo
Chris Darroch wrote:
I've been working with the 2.4 authn/z stuff a bit lately and
what I keep tripping over is that the default authorization merge rule
uses OR logic. For example, if I enable mod_access_compat and
put in a traditional:
I wonder if anyone would offer a fastfeather talk nex
12 matches
Mail list logo
