Re: workers2.properties vs JkUriSet

Hi Johnathan,

If you modify your uri mapping in workers2.properties to:

[uri:$/myapp/*]
info=My Application

http://localhost:8080/myapp/HelloWorld should work properly.
Apparently, $ is needed in order to properly parse the regular 
expression that comes after it.


Cheers,
Permaine

> -------- Original Message --------
> Subject: workers2.properties vs JkUriSet
> Date: Wed, 11 Aug 2004 13:53:08 -0500
> From: Johnathan Kupferer <[email protected]>
> Reply-To: [email protected],   Discussion of Red Hat Applications 
> Server Beta <[email protected]>
> Organization: Red Hat
> To: [email protected]
>
> As I understand, setting up URI mappings in workers2.properties is
> preferred since the file format is portable to other webservers while
> JkUriSet is Apache httpd only.  The problem I'm having is I can't find a
> way to do something like this
>
> <Location "/myapp">
>     JkUriSet worker ajp13:localhost:8009
> </Location>
>
> through workers2.properties.  The uri mapping would seem to be:
>
> [uri:/myapp/*]
> info=My Application
>
> But I've got a servlet available directly through tomcat at
> http://localhost:8080/myapp/HelloWorld and it works through mod_jk2 with
> the JkUriSet method but it doesn't with the other.  In the
> workers.properties case only http://localhost/myapp/ works properly and
> but the rest come back with an 404 not found from Apache.
>
> Am I misunderstanding how the workers2.properties mapping should work?
> If so how could I get the same effect with workers2.properties?
>
> I'm currently using mod_jk2-2.0.4-4jpp_4rh and httpd-2.0.50-2.1 on
> Fedora Core 2.
>
> Cheers,
>
> - Johnathan
>
> -- 
> rhaps-beta-list mailing list
> [email protected]
> http://www.redhat.com/mailman/listinfo/rhaps-beta-list


--
rhaps-beta-list mailing list
[email protected]
http://www.redhat.com/mailman/listinfo/rhaps-beta-list