[pca] Questions on initial setup

[Martin Paul]

little help wrote:
> On Wed, Nov 10, 2010 at 3:30 AM, Martin Paul <martin at par.univie.ac.at>wrote:
> I did try a test outside of pca and it failed as well when going to https.
> I guess I should have phrased the question better.  Are there any know
> issues with wget 1.12 when compiling for SSL?  

No, it should be fine. To verify I just tested it by extracting 
wget-1.12.tar.gz, running "./configure" and "make" on Solaris 10. The 
resulting wget binary is correctly linked against SSL in /usr/sfw/lib/ 
and I can download https://sunsolve.sun.com/patchdiag.xref with it.

But again, is /usr/sfw/bin/wget not OK for you? It saves you from the 
hassle to maintain your own copy.

> The .cgi file is simply a link to the pca file itself.  Could it be an
> ownership issue?  In regards to the httpd.conf setting - see below.
> 
>   Options Indexes FollowSymLinks ExecCGI
>   AddHandler cgi-script .cgi

That looks fine. As for ownership - the user under which httpd runs 
(webservd or nobody) must have permissions to execute the file. Try with 
755, to be safe.

> I set these based on the pca usage info. "Verify that the web server is
> configured to run CGI scripts (for apache, check the ExecCGI and AddHandler
> options in httpd.conf)."
> 
> You mentioned there was a sample httpd.conf file.  Can you let me know where
> it is- I could not seem to find it.

The one that comes with Solaris is in /etc/apache2/httpd.conf-example, 
and its default settings for /var/apache2/cgi-bin/ are fine. There are 
also two sample CGI script in this directory (printenv, test-cgi). Test 
whether these work when you copy them to the same directory as 
pca-proxy.cgi - simply access them via you web browser and check whether 
you get the output of the script (and not the script code itself).

At the end there's nothing special about pca-proxy.cgi to take or in the 
httpd configuration - it's just a CGI script, like any other.

Hope that helps,

Martin.