× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Loyd,

> Is it just as simple as changing the directory protection like this:
> Protection MYPROTECT {
> some directives
> }
> Protect /dev2objp/lookup1.pgm MYPROTECT
> Protect /dev2objp/lookup2.pgm MYPROTECT

Yes, it is.

> My second question is, do I need to enter a user and password when I move
> from lookup1.pgm to lookup2.pgm, or will it remember since they're in the
> same protection scheme?

What happens is this: when the user wants to go to a protected page, the
browser requests that page from the server.  The server reports to the
browser that an identification is required, so the browser asks the user for
identification.  The browser remembers the identification during the
session; so for the next protected page it does not have to ask the user
again.  When the browser is closed, the identification is gone as well, so
the next time a protected page is requested, the user will have to identify
him/herself again.

Joep Beckeringh





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.