For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Sim_111521's avatar
Sim_111521
Icon for Nimbostratus rankNimbostratus
Feb 05, 2014

F5 ltm Tomcat port 8080 don't display non secure content

I configured my nodes with service port 8080. For Liferay (Tomcat). I created my virtualservers for port 80 and 443. If i go to my tomcat server on port 8080, the page is displayed correct. If i go ...
Kevin_Stewart's avatar
Kevin_Stewart
Icon for Employee rankEmployee
Feb 06, 2014

Is it the warning that's telling you that you're trying to access non-secure content while in an HTTPS:// URL? Or are you talking about the warning you get when the browser doesn't trust the server's certificate?

 

If it's the former, you have to figure out what's in the headers and/or payload of the response data that still contains references to http:// URLs (vs. https://).

 

If it's the latter, you're always going to get an untrusted certificate warning if you try to access with an IP address. Aside from integrity checking, the browser also compares the requested URL to the subject name in the server's certificate. If they don't match, and they won't if you're using an IP address, you'll get the warning.