With JK 1.2.19 installed on Windows Server 2003 R2, and
given the following in uriworkermap.properties:

/Autoweb=perseus9010
/Autoweb/*=perseus9010
/autoweb=perseus9010
/autoweb/*=perseus9010

Requests are handled as follows:

/Autoweb  --> tomcat --> redirect to /Autoweb/
/Autoweb/ --> tomcat --> redirect to /Autoweb/index.html

This is operating correctly.  But:

/autoweb  --> tomcat --> redirect to /autoweb/
/autoweb/ --> IIS returns 404 (request NOT sent to tomcat)

with an explicit request to /autoweb/index.html IIS also
returns 404 without attempting to send the request to tomcat
via JK. 

What is most interesting is that reversing the uriworkermap
entries so the /autoweb lines come first reverses the
behavior.  I.e. with

/autoweb=perseus9010
/autoweb/*=perseus9010
/Autoweb=perseus9010
/Autoweb/*=perseus9010

IIS now serves /autoweb correctly but /Autoweb breaks.

*************** 

Rainer Jung replied to my posting on the user mailing list as follows:

It was not knwon (at least not to me) before your mail, but you are
right. We changed URL case sensitivity for mod_jk 1.2.19, because URLs
should be case sensitive, but we missed one place.

Could you please open a bug in bugzilla,

http://issues.apache.org/bugzilla/enter_bug.cgi?product=Tomcat%205

so that we can track the problem more easily? The bug applies to mod_jk
on all platforms and for all web server types. If multiple mount
patterns are equal except for the case, only the first url pattern will
be made active, but with the target worker of the last pattern.

Here's a workaround for your configuration:

/Autoweb=perseus9010
/Autoweb/*=perseus9010
/autoweb|/*=perseus9010

The keys on the left side are used in a case insensitive way as a key in
a hash table. If there are multiple same keys, the first key wins and
the value is set to the last one.

Since mod_jk 1.2.19 there is a convenience notation to combine
/something and /something/*. You can simple write /something|/* which
gets internally resolved as both patterns. Fortunately the hash table is
build early, so that this counts as a different key. It's only a
workaround! We'll fix the bug for the next release.