|
Rob,
First off, why are you still using the Original server? The Apache based
one is much, much better.
To answer your question, you are missing the Protect statement.
Matt
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Rob Dixon
Sent: Tuesday, January 13, 2009 10:26 AM
To: Web Enabling the AS400 / iSeries
Subject: [WEB400] Using UserID and Pawword with HTTP server (V5R1 original)
I have got to the stage with my CGIDEV2 development where I now want to
work
using User IDs. According to the manual, including
Protection /cgi-bin/stipple/* {
Authtype Basic
Userid %%CLIENT%%
PasswdFile %%SYSTEM%%
}
in my HTTPCFG file should do the trick but nothing happens. I have put
this ahead of my Exec statement which reads
Map /cgi-bin/stipple/* /QSYSLIB.LIB/E290PRDOBJ.LIB/E290G00000.PGM
This exec statement works fine.
I wish to use standard User profiles rather than a password file.
Can anyone please tell me what I am doing wrong?
Many thanks
Rob Dixon
www.erros.co.uk
www.boarstall.com
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.
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.