Thanks - I tried that earlier and again at your suggestion - no change in the behavior is noted.
This is really frustrating - there doesn't seem to be anything special about this config that should cause me such trouble. I suppose tomorrow I could try the kludge that is recommended in that thread, but given the lack of complaints about this module, I assume it is working for everyone else. Either that or no one is using it...could *that* be true? Is this module is not as useful as it seems at first glance? If it is working for everyone else, I want it to work for me, and I would prefer not to have to track my own patches whenever new versions come out naturally.... GV At 08:50 AM 10/11/2002 +0200, Vegard Vesterheim wrote: >I had a similar problem a while ago. Check out this thread: > >http://groups.yahoo.com/group/modperl/message/34266 > >----- snip - snip ------------------------------------------------- >I discovered the same thing. I think the problem is that the BEGIN >block as written, only considers parameters defined in the *main >server*. So if you have any PerlSetVar in a Virtual Server, it will >not be found. > >A kludgy workaround is to move the PerlSetVar out of any Virtual >Server sections. A better option is to reimplement the mechanism for >populating the SECRET_KEYS hash, so that Virtual Servers are handled >properly. >----- snip - snip ------------------------------------------------
