-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Mark,
On 9/12/14 11:14 AM, Mark Eggers wrote:
> Chris,
>
> On 9/12/2014 7:13 AM, Christopher Schultz wrote:
>> Daniel,
>
>> On 9/11/14 4:15 PM, Daniel Pfeiffer wrote:
>>> On 2014-09-10 22:12, Mark Eggers wrote:
>>>> I don't think that the trailing /* is valid for a simple
>>>> Location directive. If you want regular expressions you'll
>>>> have to use either LocationMatch or Location ~ (Location
>>>> followed by the ~)
>
>>> This was the decisive hint! JkMount needs /*, but Location
>>> doesn't seem to handle it well. This makes the
>>> one-argument-form of JkMount quite useless. The solution was
>>> using the two-argument-form isolated with /* and Location
>>> without.
>
>>> Still doesn't explain why it sometimes works, but I'll leave
>>> that as an exercise for mod_jk fans.
>
>> Would you please log a bug in Tomcat's Bugzilla for this? At the
>> very least, it warrants a documentation fix, and possibly a
>> review of how mappings for <Location>s are expressed/evaluated.
>
>> -chris
>
> - From the documentation:
>
> Inside Location, one omits the first argument (path), which gets
> inherited from the Location.
>
> That's where I took my clue. In Tomcat documentation fashion, the
> density of information is quite high.
>
> I personally don't have a problem with this, even though it's not
> normally my style (obviously :-p).
The problem is that most people would write:
<Location "/foo">
JkMount worker
</Location>
The "/foo" in location will handle any URL beginning with "/foo" while
mod_jk will handle a URL with /exactly/ that path "/foo". Basically,
<Location "/foo"> behaves like <Location "/foo/*"> without actually
saying it, and mod_jk will stupidly do exactly as requested, which is
not always what might be expected.
That's why the above doesn't work as expected, but using Set-Handler
does: when Location/JkMount is used, we get a bad JkMount result
(mod_jk maps only /foo, not /foo/*). If you use Set-Handler, then
/httpd/ makes the decision that the URL matches the <Location> amd
then sets the handler for it.
I really do think this warrants at least a documentation update.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
iQIcBAEBCAAGBQJUEyx2AAoJEBzwKT+lPKRYq4oP/RtFjVcKXEBH9Os4rfB/ePQm
vVpG23pASOZ3yPdd2P2QnwpW4RvTpK83R10MLyl81DkgwgSSzpb6XAKT1Gl3o6DX
+Fl0L7LyjNicwRiJWGvFWvV+KouY0WBeasvDWPWqugplxGt8Zrnf8HANQ0omVL+4
GT40hWpHCpozwFCFdJeKwCd6PF6XTQlQoTxfd4hWbGfHWtf/WjlySGDNrj7t2TNQ
dLngNEJXtu9PaM7u/ZS9F0zF2ZKaWsYrH8DJ+ym+l/R9ixruVmVD+V+98pjg9eD5
07kZ6/IosjpacvyTMHtaf4NbjUbsGpVHn4F+5Ae3JNP+XajV90xRkuhPJNyydzgq
Ws6Gp7GFkN5DjdBWwwRSPVnPOgSSatW252BgiBN1WPA0fNE4ZIJ6iqV9UdEE2Zfr
jf25bX1Qe3xPQpB0jFsQ5SnSkMlRrflDAohgVN4zxxzJw684vw3vLtNoIoEKW7bJ
M4DYlSVuaf70WlN4tLIZF7OWezyNUNF087QZff3BiJ9DXeZpS0v4i+XXU7LUmh/e
wghXW5m6Sj9No6Nbv2VZ4Y3MNsY96CLeBK1Ge0BhHJq37gt4RJnOq1co7JwMvQpK
wmpO2e0m4acLaLEkZxxmyuvnDLM83SObZo6M+WQYuWkCsUDo5XSWRvbIYYIz0SEw
7vt+Urh5OjY+xZlNJfVd
=Ncr5
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
