I've configured Virtual Hosts as you describe under apache1.3/tc2.3 as
well, and they did work ok (i.e. no crossing of context), but haven't
gone around doing it with apache2/tc4 yet.
If I do crack it I'll let you know.
My problem now is to make apache2 in one box speak with tomcat4 in
another box, with the added difficulty that the tomcat box can only
'listen' on port 21 (with the problem of it being < 1024), because of a
firewall which separates the 2 boxes (messy, I know).
I added the following rule to ipchains in the tomcat side:
-A input -j REDIRECT 8009 -p tcp -s 0.0.0.0/0 -d 0.0.0.0/0 21
which basically forwards incoming requests from port 21 to port 8009 on
the local machine where the ajp13 connector is listening).
I tested the rule by making a test apache server (on the tomcat box)
listen to 8009 and accessing it from a remote machine (ie. lynx
hostaddress:21) and it does work.
But when trying the Apache-Tomcat link it doesn't work (I get a 404 not
found)
My server.xml has:
<Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
port="8009" minProcessors="5" maxProcessors="75"
acceptCount="10" debug="0"/>
My workers.properties has the port number configured:
worker.ajp13.port=21
If I could use a port > 1024 I'd have no problem, but I'm stuck with 21
for next 3 months.
Any tips on how to make Apache2 speak with AJP13 over port 21 would be
greatly appreciated.
Dan
> -----Original Message-----
> From: Luminous Heart [mailto:[EMAIL PROTECTED]]
> Sent: 07 July 2002 04:02
> To: Tomcat Users List; [EMAIL PROTECTED]
> Subject: RE: tomcat_4.0.4 + apache_2.0.39 + mod_jk2 (linux):
> a failed attempt
>
>
> If you are able to get tomcat4 + apache2 to work with
> VirtualHosts; i.e domain2.com/app1 domain1.com/app2 but not
> domain2.com/app2 domain1.com/app1. If this seperation of
> VirtualHosts and Contexts worked for you, please ##PLEASE##
> let me know how you did it.
>
> I upgraded from apache1.3+tc2.3 where my virtualhosts
> and contexts did not cross. Now I can not get any
> virtual host or context/application to stay in its
> pin. I have posted three messages on this board with
> this regard, but it seems either noone has ran into a
> problem or no one has done similar work.
>
> So, again, if you are going that path let me know.
>
> Regards.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
