>All Mac OS servers I know of will not try to parse out CGI from a path, i.e.: > > http://localhost/cgi-bin/env2.acgi/bfisadbfsdf > >Most Unix servers will treat '/bfisadbfsdf' as extra path information, and >send it as environmental information to the CGI. But Mac servers will look >for a file called ':cgi-bin:env2.acgi:bfisadbfsdf'. > >>It's hard for me to believe that all of the Mac Web servers are "broken >>with respect to additional path information"; am I missing something? Has >>anyone ever successfully used additional path information with CGI.pm and >>MacPerl with QPQ, NetPresenz or MacHTTP? > >If I were you, I would simply make it a parameter: > > http://localhost/cgi-bin/env2.acgi?path=/bfisadbfsdf As I said, I was only playing around with the examples in TPJ so have no real need to do it at all. There doesn't seem to be any practical need for it since any information needed can be passed other ways. It just struck me as strange that the Mac servers were all like MIIS in not handling it. CGI.pm is certainly designed to use it, (cf path_info() ), but it's obviously not universal. ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch