Bug 128171 - cannot use wildcards in jk2 uri directive
Summary: cannot use wildcards in jk2 uri directive
Alias: None
Product: Red Hat Application Server Public Beta
Classification: Retired
Component: tomcat   
(Show other bugs)
Version: 1.0-beta2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Fernando Nasser
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-07-19 16:08 UTC by Peter Stiles
Modified: 2007-04-18 17:09 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-07-19 18:10:28 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Peter Stiles 2004-07-19 16:08:43 UTC
Description of problem:

Using the standalone version of tomcat

Wildcards in "workers2.properties" in the "uri" section do not work.

Please note that this problem was reported to apache and resolved in
the bug


Version-Release number of selected component (if applicable):


How reproducible:

Try to use the following in workers2.properties:

You should be able to use "http://localhost/examples/" but this
generates an apache 404 message.
The only way to make the application work is to use multiple entries
in the worker2.properties, making deployment of a web application much
more complex than is necessary and making use of the standard "admin"
and "manager" tomcat applications rather difficult.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

The issue is noted on the apache bugzilla report above. It does not
appear to have been fixed in the latest mod_jk2 available via up2date
(as of today 19th July 2004)

Comment 1 Fernando Nasser 2004-07-19 18:10:28 UTC
Duplicate of #126476

See how to specify wildcards there.

Comment 2 Peter Stiles 2004-07-20 10:48:10 UTC
Following the instructions in #126476 works, thank you very much.

As this "$" syntax is *not* mentioned in the JK documentation 
anywhere I can find, does anyone know whether this is still a "bug" 
in the JK module or whether it is an error in the documentation?

Comment 3 Fernando Nasser 2004-07-21 08:52:13 UTC
I believe it is a documentation bug.

Could you please open a bug report against mod_jk2 so someone gets it

Best regards.

Note You need to log in before you can comment on or make changes to this bug.