Bert wrote: >Ok, I'll do that. Examples of typical paths are appreciated (you may not >want to bother the list with that). Examples? I try hard to forget the settings on any server I am not using. Oh, well: /doc /text /ftp /html (May need to watch out for this sysad.) /login/web/html/enterHere (Okay, I made this one up.) /public /public-html / Most sys-ads want you to work as if your home directory is your root, but some would rather you always use relative paths. In the latter case, the '/' on the left will be missing. When login paths are required, the actual names tend to reflect the attitude (or whimsy) of the sys-ad. So there will be a lot of variation. The object is often obfuscation: Try to convince the user he doesn't want to look where you don't want him to. But in such cases sys-ads sometimes don't bother to prevent you from moving (cd ..) up beyond your own root. (Ouch.) But another attitude is to provide the user a pre-built framework to organize in. In this latter case, the sys-ad _does_ generally bother with the settings to prevent moving up beyond user's own root. (These are more experienced sys-ads.) When login directories are required in these cases, it is simply to help the novice avoid trying such things as putting html in his cgi directory. >>Do you plan to deal with proxy issues like socks servers? I, for one, >>would sure like someone to find some magic way through NT proxy servers. > >No! I'm not surprised. The settings take trial and error, and tend to be fragile. I gave up. I hope to convince the boss to let me set up a Mac or UNIX sever serving Appletalk and gating the other parts of the LAN. rees_joel@fujicomp.co.jp http://www.fujicomp.co.jp http://www.udit.gr.jp ==== Want to unsubscribe from this list? ==== Send mail with body "unsubscribe" to macperl-webcgi-request@macperl.org