in reply to Re (tilly) 1: Alternatives to PerlTransHandler?
in thread Alternatives to PerlTransHandler?

tilly has a good suggestion there. Should be pretty easy to do it that way.

'Path info' works like this: [After translation]...Apache attempts to divide the file path into two parts, a "filename" part which usually (but not always) corresponds to a physical file on the host's filesystem, and an "additional path information" part corresponding to additional stuff that follows the filename. Apache divides the path using a very simple-minded algorithm. It steps through the path components from left to right until it finds something that doesn't correspond to a directory on the host machine. The part of the path up to and including this component becomes the filename, and everything that's left over becomes the additional path information.

- from Writing Apache Modules in Perl and C, p.86, an excellent book which I would thoroughly recommend to anyone using Perl with Apache.

Another option might be to write a perl content handler. You can (I think) set this up in an .htaccess file if the permissions in Apache's main config files allow it. It's far easier than you would think - the Fierce Eagle Book goes into detail.

andy.

Update: ajt has set up Perl handlers in .htaccess files, so it is definitely possible.

  • Comment on Re: Re (tilly) 1: Alternatives to PerlTransHandler?

Replies are listed 'Best First'.
Re (tilly) 3: Alternatives to PerlTransHandler?
by tilly (Archbishop) on Nov 01, 2001 at 21:51 UTC
    It may be simple, but you need to be very, very, careful to not be fooled by file names which look like %7C%20/path/to/evil/cmd. Caveat programmer...