Hi folks, On a few of our servers here at Brandeis, we have mod_cosign configured with multiple CosignService directives. We've got things set up with a separate config file for each service, located in the conf.d directory under stock RHEL 6 Apache, which just has
Include conf.d/*.conf in its main httpd.conf file. This means we've got the equivalent top-level config of something like CosignService cerealbox CosignService milkjug CosignService applesauce running in Apache. Now let's say a user goes out to https://server.brandeis.edu/cerealbox/ where we have the URL configured in Apache with: Alias /cerealbox/ "/var/cosign/scripts/cerealbox/" <Directory "/var/cosign/scripts/cerealbox/"> DirectoryIndex index.py CosignProtected On Options ExecCGI AddHandler cgi-script .py </Directory> The intent is obviously to use the "cerealbox" service, but "CosignService cerealbox" isn't inside the <Directory> block. This being the case, how does mod_cosign know which HTTP parameters to append when redirecting to the CGI script on the cosignd server? John -- John Miller Systems Engineer Brandeis University johnm...@brandeis.edu ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 _______________________________________________ Cosign-discuss mailing list Cosign-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cosign-discuss
