Well after fooling around with it for a little while, it finally dawned on me that this isn't such a good idea. May be OK for initial contact where validation is needed but then browsing subdirectories is hindered as there is no way (that I can think of) for the redirector to know the difference between the psuedo-password and a real sub-directory.
Oh well, back to the drawing board. -- Jim Flowers<[EMAIL PROTECTED]> ---------- Original Message ----------- From: Henrik Nordstrom <[EMAIL PROTECTED]> To: "Jim Flowers" <[EMAIL PROTECTED]>, Squid Users <[EMAIL PROTECTED] cache.org> > > > While I appreciate that there are probably many ways around this > > limitation, probably the easiest for the short term that will not > > run amok will be to rewrite http://www.ftpserver.com/realuser to > > ftp://[EMAIL PROTECTED] Looks good to http and gives ftp > > what it needs. > > This will work fine and is what I was talking about in defining a > http:// URL namespace for non-anonymous FTP. Such design and also > gives a clear path on how to support anonymous FTP in the same > http://->ftp:// gateway, and makes sure that each object on the FTP > server has a unique URL by giving different users different URLs. > > Regards > Henrik
