We can: it's becomes: 'it'\''s'
> argv is always the path info, untouched. If there is no path info,
> this is "".
> argv[2....] is the decoded query info, split on spaces or ampersands.
> Example: /htbin/script/extra/path?foo=bar&bar=foo
> Command line:
> script /extra/path foo=bar bar=foo
Otherwise agreed, but I'd still wish you'd consider doing it like
I did, which would cause command line:
script /extra/path 'foo=' 'bar' 'bar=' 'foo'
In this case equal signs in values (or even names) wouldn't cause
any confusion, and spaces in values aren't a problem, either.
> If the argument to this is a URL, it is passed to the client as a 300
> If the argument to this is a path, the server will perform access
> control checks on it and send the appropriate header and document to
> the client. Should this be a virtual path, or a filesystem path? I
> currently implement it as a filesystem path for flexibility.
At least for CERN server it *must* be a virtual path, because the
rule file starts protecting already before the filesystem path is
found out. Otherwise I'd have to be able to translate filesystem
path back to virtual path which is indeterministic.
-- Cheers, Ari --