Re: Apache PerlAuthzHandler and HTML form POST vars

Thank you for updating your post. Much better.

I will now step aside and listen to the subsequent answers with great interest, as I am dealing with vaguely-similar issues right now, too.

(And, P.S. ... how about actually logging in before replying, folks ... and maybe being a wee bit less cryptic in those replies? AtDhVaAnNkCsE ... == “thanks in advance.” )

One thing that I am curious about, and truly do not myself know the answer to, is: “does it actually work to provide only an ‘authorization’ handler, in the absence of the other two?” Particularly in the absence of an “authentication” handler? (i.e. “if you do not know who I am, how do you know that I am authenticated to do anything?”) Does this “authorization” handler as-presented by the OP do an appropriate thing, or too much or too little? Does it need to be more-than-one handler?

I am an interested-party along with the OP ... not in a position to answer the question, but also-interested in what the answer is.

Replies are listed 'Best First'.
Re^2: Apache PerlAuthzHandler and HTML form POST vars by pha (Initiate) on Jan 19, 2015 at 17:07 UTC
With the deletion of the bogus line below all is right with the world. `# $query = new CGI` [download] To your expressed interest, does my experience shed any light? My handler depends on the ability to find a cookie and retrieve information from memcache none of which involves mod_perl bits in other phases. Seems not to be bothered by that lack. Thanks again for you response.	[reply] [d/l]