>> Do you have an idea why manager cannot be reached via apache ?
>>
>> Thanks
>>
>> (Port 8080 is blocked by firewall and tomcat no more uses port 8080,
>> commented in server.xml file)
>
> Sorry, Manager connexion returns a tomcat server error.
And the error is?
Tomcat version?
Did it work on p
Hi,
Our tomcat applications use port 8009 to be reached, via apache, on port
80.
Everything works perfectly but tomcat manager cannot be reached as other
applications.
We use this syntax in apache config file:
JkMount /cres default
JkMount /cres/* default
JkMount /manager defau
Hi,
Our tomcat applications use port 8009 to be reached, via apache, on port 80.
Everything works perfectly but tomcat manager cannot be reached as other
applications.
We use this syntax in apache config file:
JkMount /cres default
JkMount /cres/* default
JkMount /manager default
Hi,
We are using parameter file in our tomcat application. It is stored in
META-INF/ folder.
Everything works well, but when the server is restarted, our application
finds the parameter file no more.
We have to remove the whole application folder and re-create it.
With a re-creation the app
Tim Funk a écrit :
Then you need to extend org.apache.catalina.valves.RemoteAddrValve to check the
port (and other customizations as needed)
-Tim
I will try this.
Thanks
Sebastien Moretti wrote:
[EMAIL PROTECTED] a écrit :
I would like to deny access for my webapps through port 8080
[EMAIL PROTECTED] a écrit :
Hi,
Try removing element from your tomcat server.xml
I tried several things but it seems to be the simple one.
I would like to deny access for my webapps through port 8080 and to
allow access for other webapps via 8080 port.
But I will allow access for webapps
Hi,
after some days of tries and research I was able to run properly tomcat
(5.5.23), apache 2 and mod_jk for the same machine.
So now, my webapps are reachable with both URLs:
http://www.fake.com/webapps
or
http://www.fake.com:8080/webapps
As I understood mod_jk, apache/mod_jk looks in loca
