PerlSetVar behaviour within directive

2009-01-23 Thread Pat Downey
Hi I am trying to set variables for the Atlassian Crowd PerlAuthzHandler based upon the type of request that is being received by the apache server. The chunk from my httpd.conf file looks something like the following: AuthType Basic AuthName "Crowd Auth" PerlAuthenHandler Apache::CrowdA

Re: PerlSetVar behaviour within directive

2009-01-23 Thread Torsten Foertsch
On Fri 23 Jan 2009, Pat Downey wrote: >   >     PerlSetVar CrowdAllowedGroups reader,writer >     Require valid-user >   >   >     PerlSetVar CrowdAllowedGroups writer >     Require valid-user >   > > > What I'd like is for members of the reader or writer groups to have > GET access and only m

Re: PerlSetVar behaviour within directive

2009-01-23 Thread Pat Downey
2009/1/23 Torsten Foertsch > PerlSetVar CrowdAllowedGroups reader,writer > Require valid-user > >PerlSetVar CrowdAllowedGroups writer > > Thanks for the response Torsten, unfortunately this still exhibits the same behaviour that I was experiencing before. In both your example and the

Re: PerlSetVar behaviour within directive

2009-01-23 Thread Michael Ludwig
Pat Downey schrieb: I guess I might have to modify the module to recognise another couple of variables say CrowdAllowedWriteGroups and CrowdAllowedReadGroups and not worry about the directives as I think I'm using them in a way that wasn't intended. That's what I think, too. The relevant conc

[Travel Assistance] Applications for ApacheCon EU 2009 - Now Open

2009-01-23 Thread Philip M. Gollucci
Subject: [Travel Assistance] Applications for ApacheCon EU 2009 - Now Open From: Tony Stevenson Date: Fri, 23 Jan 2009 13:28:19 + To: travel-assista...@apache.org The Travel Assistance Committee is now accepting applications for those wanting to attend ApacheCon EU 2009 between the 23rd a

t/hooks/authen_basic and t/hooks/authz errors

2009-01-23 Thread Christian M. Probst
Hi, folks. I have the following errors when running "make test". I have seen a similar error discussed in the list in Nov 2008, but as it was mentioned that it could be an error related to Apache 2.2.10 and I am running Apache 2.2.6 in Solaris 10, I think there is something else happening here. He