|
Wayne,
If the user is challenged to login when the cgi welcome page is
requested, before any response is received, then REMOTE_USER must be
populated and available to the cgi program. The qsh cmd(set) program
should prove this.
Peter
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Wayne McAlpine
Sent: Sunday, 22 March 2009 14:33
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] Environment Variables
Peter, there is no initial html document. The url is to a cgi program
that generates the welcome page.[mailto:web400-bounces@xxxxxxxxxxxx]
Peter Connell wrote:
Wayne,
Just a thought.
Are you certain that the page you are concerned with is in fact a url
that is protected by the authentication block in the Apache config?
For example, you may have first requested a page that required you to
authenticate but subsequently requested a page that does not.
REMOTE_USER will show up in the first but not the second.
Peter
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx
On Behalf Of Wayne McAlpineother
Sent: Saturday, 21 March 2009 15:11
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] Environment Variables
Peter, I'm doing this in the same main CGI program that retrieves
environment variables, so I know that the mechanism works.
I'm starting to wonder if there is an Apache configuration directive
that may be missing to allow REMOTE_USER to be populated by the
validation list value. Here is what I have in httpd.conf:
Require valid-user
ServerUserID QTMHHTTP
PasswdFile ICFLIB/UCCWEB
AuthType Basic
AuthName "Louisiana Secreta
SSLRequireSSL
SetEnv HTTPS_PORT 4430
Options +ExecCGI
Peter Connell wrote:
If you are not retrieving it then you must have an issue with
the mechanism you are using to retrieve it. It's there for all to
retrieve.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.