bject was :
Subject: Re: [2.4.39] [mod_auth_form]
[mod_session_crypto] Cookie management performance
Cheers,
Vincent Deffontaines
(alternate email address : gry...@apache.org)
--
Notre liberté repose sur ce que les autres ignorent de notre existence
Alexandre Soljenitsyne
ers_out, "Cache-Control", "no-cache,
private");
if (r->user) {
ret = dbd_save(r, r->user, r->user, z->encoded, z->expiry);
CJ
[1]:
https://httpd.apache.org/docs/trunk/mod/mod_session.html#sessionexpiryupdateinterval
[2]:
http://svn.apa
Greetings,
The root observation that makes me open this subject is the following :
Using mod_auth_form + encrypted cookies to manage a web application
authentication gets httpd's auth cookie to be reset by the server at
each and every authenticated request. On a website with a number of
users
Le Thu, 18 Apr 2013 11:29:29 -0400,
Rich Bowen rbo...@rcbowen.com a écrit :
On Apr 18, 2013, at 11:09 AM, Igor Galić wrote:
From an IRC conversation in #httpd and #httpd-dev emerged the
idea to interpolate %{variables} in all directives.
According to sf we have somewhere a ~10 line
Greetings,
While providing support on IRC, I noticed that FallbackResource lacks a
'turn-off' switch.
Since it works in per dir config, it seems sane that it could be
valuable to turn it off in chosen subdirs.
This one liner patch adds support for the keyword 'disabled' (stolen
from userdir).
Of
Greetings,
While providing support on IRC, I noticed that FallbackResource lacks a
'turn-off' switch.
Since it works in per dir config, it seems sane that it could be
valuable to turn it off in chosen subdirs.
This one liner patch adds support for the keyword 'disabled' (stolen
from userdir).
Of
for releases that will be coming ?
Regards,
gryzor
Vincent Deffontaines
--
I never look behind me, my troubles will be few
Supertramp
On 19/07/2012 12:01, Graham Leggett wrote:
On 19 Jul 2012, at 11:57 AM, Vincent Deffontaines wrote:
The CHANGES file does not describe the date of each release in its
content. (example : http://www.apache.org/dist/httpd/CHANGES_2.4 )
Currently, it seems to me the way to find out when httpd
patch, unsure whether it should be
commited separately ?
Please comment and correct me if needed.
Vincent Deffontaines
Index: docs/manual/mod/mod_proxy.xml
===
--- docs/manual/mod/mod_proxy.xml (révision 1059390)
+++ docs/manual/mod
On 08/12/2010 18:07, Eric Covener wrote:
... and assume overlaps are intentional opt-in to name-based vhosts?
The selection algorithm would not change, meaning you'd still only be
selecting from the best ip-based match.
We'd lose the warning about overlapping vhosts, and maybe incur some
Greetings,
A stupid config example to make my point :
Loglevel debug
RewriteEngine On
RewriteRule .* - [F]
This denies all requests, and logs nothing at all in error log to
explain that behavior.
This is contrary to a common Apache behavior about all non 2XX answers
triggering an
Dan Poirier wrote:
Lars Eilebrecht l...@eilebrecht.net writes:
Vincent Deffontaines wrote on 2009-02-08 13:20:23:
While reviewing Lucien's french translation for the trunk performance
tuning guide (misc/perf-tuning.xml), it has come to my understanding
that this document contains extremely
Greetings,
While reviewing Lucien's french translation for the trunk performance
tuning guide (misc/perf-tuning.xml), it has come to my understanding
that this document contains extremely old, and probably outdated,
information.
URL for the HTML version is
Greetings,
Trunk can log connection source port by using in Logformat : %{remote}p.
2.2 currently does not support that (only logs the destination port of
the connection).
Included is a very simple (trivial) backport of that functionnality from
trunk to 2.2.
Tested, works for me.
Vincent
author of the patch, which André applied.
Shortly after the patch was accepted in 2.0, I sent a documentation
patch for 2.0.
Reply I got was that 2.0 documentation was not important, and doc
patch would not be applied.
As far as I know, the patch *is* applied on 2.0.
BR,
Vincent Deffontaines
Greetings,
On the process of setting up a [apache2] reverse proxy, I am having this
problem :
I would like to set a RequestHeader depending on some conditions.
It seems that, though the Header directive accepts an env var as
condition, this cannot be used with RequestHeader, which seems to be a
André Malo a dit :
* Nick Kew [EMAIL PROTECTED] wrote:
On Thu, 25 Mar 2004, Vincent Deffontaines wrote:
As this seems quite simple to implement, here is my question : would a
patch implementing env vars in RequestHeader be accepted?
I would support that patch.
Since you're new
17 matches
Mail list logo
