I'm currently trying to port mod_auth_script, a Apache 1.x module that
used the result of a script to allow/deny an authentication. The issue
I'm currently running into is sub requests - it seems that whatever
output and return code my module's sub request returns is what gets
sent to the web
Dave Ingram wrote:
First off, if this isn't the correct place to ask this then I apologise,
but it seemed the most appropriate list. If there's somewhere more
appropriate, please let me know.
I've had a quick look for some information on accessing a database via
APR, and after glancing through
Nick Kew wrote:
Dave Ingram wrote:
First off, if this isn't the correct place to ask this then I apologise,
but it seemed the most appropriate list. If there's somewhere more
appropriate, please let me know.
I've had a quick look for some information on accessing a database via
APR, and
On Fri, Aug 29, 2008 at 20:52, Roy Wellington [EMAIL PROTECTED] wrote:
I'm currently trying to port mod_auth_script, a Apache 1.x module that
used the result of a script to allow/deny an authentication. The issue
I'm currently running into is sub requests - it seems that whatever
output and
Hi Peter,
I've fixed my problem. Your advice was really helpful, the only thing I had to
change was to replace server/exports.o with server/protocol.o modules.o
buildmark.o server/provider.o server/util_xml.o server/error_bucket.o and
everything works fine.
Thanks again for your help
Steven
Den Thursday 28 August 2008 19:45:10 skrev Kaspar Brand:
I wrote:
When I added the second condition to the first if statement, I was
assuming that the default for auth.verify_depth is UNSET as well.
However, it's initialized to 1 (i.e. SSL_CVERIFY_OPTIONAL)
On Aug 28, 2008, at 9:41 PM, Nicob wrote:
Hello,
I'm actually trying to setup a SSL reverse-proxy based on Apache 2.x
and
mod_ssl and it seems there's a bug in the verification of the CRL.
If a CA changes its keys before expiration, the CRL is now signed by
the
new key and include
On 8/28/08 8:45 PM, Jess Holle [EMAIL PROTECTED] wrote:
Possible solutions include:
Having an option to have a background thread ping the backends rather than
allowing normal requests to do so.
One way to possibly do this is to have a single health checking that's in
the parent that can
