![]() ![]() It just forwards traffic from websocket to Java server TCP connection.īut it has its own SSL certs setup. The webapp needs to communicate with Java TCP server through websocket so we have a webSocket server written in nodejs. # Defining a worker named ajp13 and of type ajp13 # - An ajp13 worker that connects to localhost:8009 Only thing that's added to nf is JkMount /* ajp13 nf - has nothing but default since SSL is disabled. # Removed cluster config since they're all default Server.xml contains only these enabled lines, rest of them are commented out or defaults: Modified web.xml to set http-only to true and secure bit to true on tomcat server.Īnything else that needs to be done? I've spent a day trying to troubleshooting this and couldn't figure it out yet.Disable 8443 ports and all redirects to port 8443 and listen only 8080.What settings are required to make this work? I've tired the following: I can't get rid of Apache in between and it is really needed for the app temporarily. Setup which works fine: Nginx controller (SSL passthrough) -> Apache (HTTPS port 443) -> Tomcat (HTTPS port 8080). I spoke to dev they mentioned it could be cookie issues.Ĭurrent setup which is not working: Nginx controller (SSL termination) -> Apache (HTTP port 80 ) -> Tomcat (HTTP port 8080). Apache server handles static content and forwards all JSP related to tomcat.įor some reason the webapp doesn't work on the first try (website works fine though) when doing SSL termination but if I reload the page and try to use the app again then during this second attempt everything works fine (means it doesn't load some of the automatic functions on first attempt and can be reproduced by clearing the cache and logging in). ![]() So we have Nginx Controller which handles SSL termination and passes HTTP traffic to Apache server. I'm testing our app on a kubernetes cluster.
0 Comments
Leave a Reply. |