Use of Tomcat's Remoteaddrvalve

Having discussed the use of multiple Tomcat accesslogvalve, today, let's look at the use of remoteaddrvalve.

We know that Tomcat has several default applications, including manager and admin. Sometimes we want to use these two applications to publish our own applications, but do not want outside people to access it (because it is not safe), we can move out of the Remoteaddrvalve:

　　1) server.xml Find path= "/manager" field, add

<valve classname= "Org.apache.catalina.valves.RemoteAddrValve" allow= "allows the manager to access IP" deny= ""/> "

　　2) Server.xml find path= "/admin" field, add

<valve classname= "Org.apache.catalina.valves.RemoteAddrValve" allow= "Allow admin access to IP" deny= ""/> "

Oh, it's done. I used to think that only WebLogic server such a function!

<valve classname= "Org.apache.catalina.valves.RemoteAddrValve" allow= "Allow admin access to IP" deny= ""/> "

Oh, it's done. I used to think that only WebLogic server such a function!

<valve classname= "Org.apache.catalina.valves.RemoteAddrValve" allow= "allows the manager to access IP" deny= ""/> "

2) Server.xml find path= "/admin" field, add

<valve classname= "Org.apache.catalina.valves.RemoteAddrValve" allow= "Allow admin access to IP" deny= ""/> "

Oh, it's done. I used to think that only WebLogic server such a function!

<valve classname= "Org.apache.catalina.valves.RemoteAddrValve" allow= "Allow admin access to IP" deny= ""/> "

Oh, it's done. I used to think that only WebLogic server such a function!