On Wednesday, 04. October 2006 12:31, [EMAIL PROTECTED] wrote:
> Lo all,
>
> There's a bit of a difference as outlined below.
> It doesn't seem to be causing problems tho.
> Any url seems to have a "/" put on the end for some reason.
> fred is set up in axkit.conf as a location.
Locations are usually interpreted as directories. This stems from a
fundamental difference between the Apache location mechanism and AxKit2's.
In Apache, <Location> was simply an URI match and had no influence on
uri-to-file mapping. In AxKit2, each <Location> maps to it's DocumentRoot
(either explicitly configured for that location, or inherited), so the
location is usually resolved to a directory. Example:
DocumentRoot /foo/bar
<Location /baz>
</Location>
In Apache, URIs would be mapped this way:
/ -> Dir /foo/bar, URI /
/baz -> Dir /foo/bar, URI /, path_info /baz
In AxKit2, it works like this:
/ -> Dir /foo/bar, URI /
/baz -> Dir /foo/bar, URI /baz/
because any URL starting with "/baz" will do path lookups beginngin
with "/foo/bar" again. This is by design, because it allows you to easily
share a common web data root among all web applications (which is expected to
be the common case).
To get Apache-like behaviour, add one directive to each <Location>-block:
Path ""
(It specifies the prefix to be stripped from URIs before filename resolving
takes place, so this line disables the AxKit2 mechanism.)
--
CU
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
