Skip Menu |

This queue is for tickets about the Apache-AuthCookieDBI CPAN distribution.

Report information
The Basics
Id: 4847
Status: resolved
Priority: 0/
Queue: Apache-AuthCookieDBI

People
Owner: Nobody in particular
Requestors: william [...] knowmad.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 1.19
Fixed in: 2.01



Subject: Using PerlSetVar for SecretKey fails inside of VirtualHost
Using this module as described in the Synopsis fails if the PerlSetVar WhateverDBI_SecretKey directive is contained within a VirtualHost. The reason for this appears to be due to the fact that these variables are not available during server startup[1]. One workaround is to place the PerlSetVar WhateverDBI_SecretKey directive outside of the VirtualHost settings. This can be a nuisance, esp. when dealing with a multi-vhost server. The other workaround is to include the Apache::AuthCookieDBI module inside of a <perl> section as follows: <perl> use Apache::AuthCookieDBI; </perl> The PerlSetVar directive still needs to be placed *before* the <perl> section. I do not know if this solution would work for multiple vhosts that use AuthCookieDBI. It seems likely that the module would get loaded by the first vhost before seeing the PerlSetVar directive for the second vhost. Seems like there should be an alternate solution to reading the keys in the BEGIN block. Thanks, William [1] http://aspn.activestate.com/ASPN/Mail/Message/modperl/1920838
Hi Matisse, I'm just going through my old posts and trying to update them. I'm not sure if this issue still applies as I've never used this module with more than 1 vhost. I may have also been confusing SecretKey with SecretKeyFile as I definitely had problems with using the later. I can say that using PerlSetVar WhateverDBI_SecretKey does work inside of a vhost under Apache2/mp2. My point about using multiple vhosts is kinda irrelevant as different realms could be used. You can close this ticket. Thanks, William
Thanks. I will look into this. For some reason I am not getting email when entries are made here in rt, they are still going to the original module maintainer, Jacob, who has been forwarding them to me.