New answers tagged

0

I suggest you block direct access to the server as that's a back door into the server and a DDOS attack. I would do this by putting the Tomcat instance into a private subnet. If you must have it in a public subnet I would ensure only a few things can reach it - the ALB (using VPC CIDR range is easiest) and specified IPs. If it's private you can use AWS ...


1

With John on this one, you're likely missing or have incorrectly set up your ingress rule. You'll want to use something like below, though not exact. Direction: Ingress Action: Allow Targets: Specific target tags input a network tag assigned to the VM IP Range: IP range(s) you want to be able to access your app Protocols and Ports: 8080


0

The version info for the Apache server is defined in code, not in configuration or an external file. To change that you would need to fork the repo and build your own version after making the change.


2

This is an educated guess. I think this might be a case of both the Manager part and Apache using HTTP authentication headers for authentication. When the client connects to http://localhost/manager, Apache asks for authentication credentials for LDAP authentication. The client will then send the authentication information to Apache, which accepts the ...


1

based on https://stackoverflow.com/questions/5808206/how-to-fix-tomcat-http-status-403-access-to-the-requested-resource-has-been-den it seems that you are missing a role definition. In the tomcat-users.xml file add a user with the role manager : <role rolename="manager"/> <user username="admin" password="admin" roles=&...


Top 50 recent answers are included