-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 05 April 2003 00:10, Kruse, Matt wrote:
For every request to Apache:
1. Parse the cookie coming in via the request header
2. Pull out each value (ex: NAME=bob;TITLE=boss)
3. Convert them to HTTP Request Headers
4. Pass the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 03 April 2003 20:33, Perrin Harkins wrote:
Of course you could also just totally prevent people from logging in
again if there is already an active session for that user, but that
will cause problems because your sessions will not get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 06 November 2002 15:19, Eric L. Brine wrote:
HTML 4.01 also has a section on META and http-requiv. However, the
only reference to refresh is: Note. Some user agents support the
use of META to refresh the current page after a specified
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, it gets weirder. The following script produces the leak. If I
comment out the install_driver line, I get a big old segfault! Same
if I comment out the Apache::DBI line in addition. This works with
plain apache, or apache-ssl.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 16 October 2002 20:25, Keith G. Murphy wrote:
By should, do you mean that the problems with the loadable module
overall are so well-known that no one in his right mind should ever
use it?
Yes. The problems with DSO mod_perl are well
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 16 October 2002 22:52, Keith G. Murphy wrote:
It's not like it was an obvious problem: I only got the DSO to leak
when loading the Pg driver. That's pretty obscure.
Have you tried to connect() without loading the Pg driver first?
