I was looking into caching of user credentials, but I think I might be missing
something.
The call ap_authn_cache_store seems to store user credentials which will help,
if you have
a directive like 'Require valid-user', but it won't help for directives like
'Require group admin'.
Am I right?
Hello,
http://httpd.apache.org/docs/2.4/mod/mod_authn_socache.html
There are 2 things I want to mention:
1) cacheing is not a word. It should be replaced with caching on the entire page
2) AuthnCacheSOCache Directive: If not set, your platform's default will be
used.
There's no indication
On 17.06.15 18:56 , Eric Covener wrote:
Sounds right. The authn in the name is shorthand for authentication
(vs authorization). It seems possible to shoehorn other data into this
cache though, but it's not clear to me what it adds using socache
directly.
The problem is that I don't know how.
Seems like a good idea to not place the ALPN patches into 2.4 - yet.
During my tests, I discovered that the order of my vhost definitions affected
the certificate chosen - when ALPN was in play. After some analysis, the
following seems to occur. This is to make the mod_ssl people here aware and
On Wed, Jun 17, 2015 at 8:21 AM, Stefan Eissing
stefan.eiss...@greenbytes.de wrote:
1. connection, setup for base server and defaults
2. client hello arrives
3. ALPN callback is invoked by openssl
4. ALPN protocol is chosen, this triggers the server answer
5. SNI callback is invoked by
I have updated the bugzilla ticket since this was committed in
r1684900 and a backport to 2.4.x is already proposed.
Regards,
Yann.
On Wed, Jun 17, 2015 at 11:06 AM, Mario Brandt jbl...@gmail.com wrote:
Hi Nick,
please add a unified diff file to the bug and add the keyword PatchAvailable
Hi Nick,
please add a unified diff file to the bug and add the keyword PatchAvailable
Cheers
Mario
On 11 June 2015 at 13:31, Nick Gearls nickgea...@gmail.com wrote:
Hi all,
Can anybody have a look at this trivial bug waiting for months?
The bug is obvious and the fix is a one line change.