Webjames .htaccess problem

Webjames is not obeying certain .htaccess files in my local website. For instance:
DirectoryIndex 001.php
Options -Indexes
This is supposed to mean the home page in that directory is “001.php”. Webjames is happy with “!home.php” and various other names but does not want to serve 001.php (maybe because of the numbers?). Instead it produces an autoindex, even though the minus in “-Indexes” should prevent autoindex.

(That autoindex shows 001.php among the other files, and if I click it, Webjames does serve it.)

In the log file (!Syslog.Logs.Webjames) I see these lines:
Unknown attribute: options
Unknown attribute: directoryindex
Unknown attribute: indexoptions
Unknown attribute: indexignore
Why are these unknown?

This has been happening since I upgraded Webjames from Chris Gransden’s 2013 patch to his 2016 patch (thanks to someone in this forum who gave the secret link).

Is there some setting I need to change? I’m boggled.

(The identical files uploaded to my ISP webhost behave correctly.)

Why are these unknown?

Because WebJames is not Apache.

Ignore everything you read online about the content of the htaccess file. That which is described in WebJames’ help is that which is supported (basically it’s a restricted form of the Attributes file).

The identical files uploaded to my ISP webhost behave correctly.

Because that is Apache.

If I were you, I’d configure WebJames to refer to a /webjames file and leave /htaccess for the sole use of Apache (it’s a setting in the Config file).

WebJames is not Apache. Ignore everything you read online about the content of the htaccess file.

This is in Webjames.Help in its History section:
    0.26 (19/10/2000)
    • added support for htaccess files

As I said earlier, the 2013 (and 2007) versions of Webjames did obey my .htaccess files in exactly the same way as Apache does and still does.

My problem is with the 2016 Webjames update (which I only in the past 10 days discovered and installed); maybe I need to revise some obscure setting in Wj, but what?

The help also says:

The htaccess files are in the same format as the attributes file, but act as if the whole file was surrounded by a <directory dirname> section, where dirname is the directory the htaccess file is in. It can contain <files> and <filesmatch> sections, but not <location> or <directory> sections.

Here is the entirety of my .htaccess file in the directory in question. Nothing complicated. Webjames 2016 does not obey either of the two commands (# is a comment), whereas Webjames 2013 and Apache do obey them.
    DirectoryIndex 001.php
    # disable autoindex
    Options -Indexes

Why is the 2016 incarnation of Webjames throwing up the “Unknown attribute” stuff in the log, whereas the 2013 Webjames and Apache are happy?

!WebJames was re-complied some time ago for Ras Pi 3 comatibility. Maybe, it was re-complied using an out-of-date source code.

The “re-compiled for Pi 3” version which I have is dated 08 October 2016. I downloaded it in May 2017. It did what I wanted, so I did not do any further regression testing (like htaccess).

This looks like something we will have to look out for when we need a version for the Pi 4.

I dug around in my backups and found some old Syslog files for Webjames, which would date from when I was using the 2013 incarnation of it (ie, ancestor of the 2016 version you mention). And I’m surprised to find the lines like “Unknown attribute: directoryindex” in the OLD logfile too. So I’m wrong in my earlier posts today about this being new in the 2016 version of Webjames.

Perhaps when Alex Waugh added support for .htaccess files way back in 2000 (see my quote from History), it was before the .htaccess HQ had invented commands such as “directoryindex” and “options”? I have no idea.

I second and third the motion that out-of-date sources be revisited in compiling the eventual Pi4 version of Webjames. And the built-in Autoindex module should be opened for customization by the user (perhaps by a reference in Attributes).