Re: [Htp-discuss] Absolute paths don't work on UNIX?

[Jochen H. <hoe...@gm...>]

Hello,

>
> On Tue, Apr 8, 2014 at 3:47 PM, Daniel Goldman <dgo...@eh...> wrote:
>>
>> htp 1.16 is version. Apparently because htp allows /option to be a
>> command line option, because / can be used to indicate an option, htp
>> seems to have a problem with absolute paths on the command line.
>>
>> Works OK:
>> $ htp temp.x temp2.x
>>
>> Produces error message about "unknown option":
>> $ htp /path/temp.x /path/temp2.x
>>
>> Other than not using absolute paths with htp, any suggestions?

I always used relative paths so I did not notice this problem.


2014-04-08 22:24 GMT+02:00 Robert Hood <bo...@th...>:
> Maybe you could recompile it removing the slash as an option delimiter. That
> way, you could still specify options by using dashes, but you'd avoid that
> symbol conflict.
>
> There's also the option of using a response file instead of manually sending
> filenames...

Using a response file does not work, as it has the same problem.
Updating the source code to not accept '/' as an option delimiter is
easy, just search for '/' in htp.c (with quotes; it occurs twice) and
remove the corresponding branches (from || to the next closing
parenthesis).  Options will still be recognized if they are prefixed
with '-'.

I'm not sure if I should make this the default behaviour under unix.
This may break some existing script.  Another possibility would be to
assume that it is a path, if there is no option with that name, or if
there is more than one '/'.  This is a bit harder to do and a bit
ugly.

Regards,
  Jochen