On Sunday, 24. September 2006 11:00, Lars Skjærlund wrote:
> However, I might have misunderstood you: When I complained that
> DirectoryIndex would only take a single parameter - and that I needed
> more - you answered in two ways: By adding an error message stating that
> you cannot have more than one parameter, and by telling me that I should
> use typeless_uri instead. You also assured me that the latter would
> solve my problem.
Well, the error message was not in response to your request. It was part of
the config system rewrite. It was an improvement, because previously you
didn't get an error message, but still only one DirectoryIndex.
Moreover, I suggested you try typeless_uri to see if it suits you. If not,
well, it was just an attempt at being helpful. It was not a suggestion that
this is the only way to go.
> But it won't: First of all, I want to use .odt files for ordinary
> webcontent, and your typeless_uri doesn't allow for that. I could modify
How so? What in typeless_uri prevents you from using .odt as extension?
> it, of course, but then we're back to the old story. But at the same
> time, simply adding .odt as an extension on your list still wouldn't
> solve my basic problem, as I would like to be able to add an arbitrary
> number of extensions for different fileformats - and the crucial problem
> for me would be that I sometimes need tight control over the order that
> extensions are checked.
So where is the problem? As the documentation for typeless_uri says, the
configuration directive URIExtensions configures what extensions to try, and
in what order.
> Apache has worked like this for years, you have the choice and the
> flexibility to do so if you please, but it appeared to me that your
> message was: No, either you use a single index file, or otherwise use
> typeless URIs. Whilst I can follow and sympathise with the latter, it
You aren't forced to use typeless URIs for all of your site. While they _are_
an improvement to your site, no one forces you to use them exclusively. If
you just need the DirectoryIndex funtionality, go ahead and use it just for
that. Any URL that points to an existing file won't be touched by
typeless_uri.
> my $mtime = $client->headers_out->header("Last-Modified") ?
> $client->headers_out->header("Last-Modified") :
> http_date((stat(_))[9]);
This is obvious and logical, so I have added something like that to
serve_file.
--
CU
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
