- Original Message -
On Wednesday 02 January 2013, Eric Covener wrote:
On Wed, Jan 2, 2013 at 4:02 PM, Stefan Fritsch s...@sfritsch.de
wrote:
On Wednesday 02 January 2013, Jim Jagielski wrote:
For *real* improvement, wouldn't storing in socache be
the optimal method?
On Saturday 05 January 2013, Igor Galić wrote:
No, mod_authn_socache only caches the lookup of the password
hash. It avoids having to open the password file/dbm/whatever
but it still calls apr_password_validate() every time. Maybe it
should be extended to also cache the real password and
On 05/01/2013 11:52, Igor Galić wrote:
- Original Message -
On Wednesday 02 January 2013, Eric Covener wrote:
On Wed, Jan 2, 2013 at 4:02 PM, Stefan Fritsch s...@sfritsch.de
wrote:
On Wednesday 02 January 2013, Jim Jagielski wrote:
For *real* improvement, wouldn't storing in
On Wednesday 02 January 2013, Eric Covener wrote:
On Wed, Jan 2, 2013 at 4:02 PM, Stefan Fritsch s...@sfritsch.de
wrote:
On Wednesday 02 January 2013, Jim Jagielski wrote:
For *real* improvement, wouldn't storing in socache be
the optimal method?
Yes. I fear there may be some
Dear All,
First of all, congratulation on the release of 2.2.
I use mod_auth_pgsql at http://anyterm.org/my.html, and found a problem
earlier in the year. To get reasonable performance you need to use the
module's caching mechanism, but this cache is not flushed or updated
when the database
On Saturday 03 December 2005 11:39, Phil Endecott wrote:
Has anyone looked at this? If no-one is working on this and you think
it would be a useful feature to add, I may be able to write something
with a bit of help.
This is beyond the scope of what we've done, which is why you didn't
find
Hi Phil,
A while back I wrote a auth wrapper which used a MD5 hash inside a
cookie to determine if the user was authenticated. If the cookie was
invalid or not present it would fall back to the regular auth method (in
your case a DB hit).
It also had a bit which sat just after the
