|
<snip> You can use the server's protection function to control which clients can use your server as a proxy. This is part of controlling access to your server. <end snip> I've never used the HTTP server as a proxy, but I have defined a few protection setups. I might at least get you started in the right direction. The best source of information I know of, is the HTTP Server Webmasters Guide - available from the on-line library. I've downloaded the PDF version. The form provided by the *ADMIN server is not intuitive. The "protect" directive and related subdirectives in the HTTP Server Configuration file cause the HTTP server to request a User ID and Password before allowing access to a URL. The User Id can be an AS/400 user profile, or an ID defined in an access control list. The protect directive works in combination with a pass directive. The pass directive opens access to a specified URL template, while the protect directive ensures that only authorized used have access to that URL. Hope that gets you started. Nathan M. Andelin +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.