Good afternoon,
On 27/8/03 at 9:37 AM -0400, Michael [EMAIL PROTECTED] wrote:
The reason this question is mod_perl related is that he is doing the
initial authentication using mod_perl, and is creating a cookie based
ticket. But he wants that ticket to also be accepted by a
non-mod_perl enabled
Good afternoon,
On 27/8/03 at 9:45 AM -0400, Michael [EMAIL PROTECTED] wrote:
Any other suggestions?
I'd think you'd want to have the same authentication process for both, and a
shared database (or something) to store the session data. Have the front-end
do the login part, pass the client to
Good morning,
On 26/8/03 at 8:26 PM +0200, Thomas Klausner [EMAIL PROTECTED] wrote:
Hi!
On Die, Aug 26, 2003 at 09:06:05 +1000, Charlie Garrison wrote:
I need to protect resources in both the static (proxy) front-end and
the mod_perl back-end. I have been using standard http authentication
On Tue, Aug 26, 2003 at 21:06:05, Charlie Garrison said...
The second one, Cookie Authentication with MySQL, looks like a very good
option, except for two issues. Fist, it doesn't support the 'require group...'
directive. And second, it doesn't appear to cache mysql connections so I am
Quoting Michael [EMAIL PROTECTED]:
On Tue, Aug 26, 2003 at 21:06:05, Charlie Garrison said...
The second one, Cookie Authentication with MySQL, looks like a very good
option, except for two issues. Fist, it doesn't support the 'require
group...'
directive. And second, it doesn't appear
Good afternoon,
On 27/8/03 at 2:49 PM +1000, Cees Hek [EMAIL PROTECTED] wrote:
Umm, use Apache::DBI, that's what it's for.
It was easy to miss in the email if you skimmed it, but he is looking for a C
based module, so any perl based solutions are out.
The reason this question is mod_perl
Good afternoon,
On 27/8/03 at 12:05 AM -0400, Michael [EMAIL PROTECTED] wrote:
The second one, Cookie Authentication with MySQL, looks like a very
good option, except for two issues. Fist, it doesn't support the
'require group...' directive. And second, it doesn't appear to cache
mysql
On Wed, Aug 27, 2003 at 14:49:05, Cees Hek said...
It was easy to miss in the email if you skimmed it, but he is looking for a C
based module, so any perl based solutions are out.
Whoops, you're right, I did just skim it.
The reason this question is mod_perl related is that he is doing the
On Wed, Aug 27, 2003 at 15:45:11, Charlie Garrison said...
I haven't been 100% happy with any of the systems written by other
people so I've always just written my own. It's a rather simple
Do you also write the apache module for the frontend server? I'm very
competent at perl, but not
Good evening,
I have done a bit of research and found some possible solutions, but none of
them seem to be exactly what I want. First, the problem I need to solve...
I need to protect resources in both the static (proxy) front-end and the
mod_perl back-end. I have been using standard http
Hi!
On Die, Aug 26, 2003 at 09:06:05 +1000, Charlie Garrison wrote:
I need to protect resources in both the static (proxy) front-end and the
mod_perl back-end. I have been using standard http authentication which works
pretty well except for not allowing a proper logout function and some
11 matches
Mail list logo
