|
Are youy using .htaccess or ..htaccess? Regards, Jim McLean jim.mclean@xxxxxxxxxx (519)252-4415 ext. 502 |---------+-------------------------------------------------> | | "Chris Piper" <Cpiper@xxxxxxxxxxxx> | | | Sent by: | | | web400-bounces+jim.mclean=farrow.com@m| | | idrange.com | | | | | | | | | 20/08/2004 11:29 AM | | | Please respond to Web Enabling the | | | AS400 / iSeries | | | | |---------+-------------------------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: <web400@xxxxxxxxxxxx> | | cc: | | Subject: [WEB400] Username passwords | >------------------------------------------------------------------------------------------------------------------------------| Another silly question, but how do I protect, user name password required pages. I have tried using the Location and File tags, imbedding the ..htaccess file in the directory and can get nothing to work. We have a page http://servernamehere/cgibin/po.d2m/input, which maps in Apache to QSYS.LIB/EXTCGIBIN.LIB/DB2WWW.PGM/po.d2m/input. When I try to add the user name password protection it never seems to take. I have placed it inside the directory for QSYS.LIB/EXTCGIBIN.LIB/DB2WWW.PGM, outside of it, in a ..htaccess file in the actual folder where the script is stored, and nothing works. Any help would be great. Thanks, Chris _______________________________________________ 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.