Karen Hartley wrote:I have just configured my local Tomcat to support https in order to test Firebase messaging on my web app. I am able to get to my app now via https - however, when Firebase tries to load I get a bunch of errors indicating that there are too many redirects going on for Firebase. The only redirect is whatever is being done to allow https.
Is there a way to get Tomcat to handle https without incurring redirects in the process?
Welcome to the JavaRanch, Karen!
I don't think that Tomcat itself generates redirects for HTTPS. Generally speaking, you direct HTTP to port 8080 (by default) and to port 8443 (if you have default HTTPS). You will have some redirection done if a user requests a URL whose transport-guarantee in the WEB-INF/web.xml demands secure transport, but actually, I'm not sure how much of that is generated by Tomcat and how much simply bounces if you don't use the right protocol to begin with. That would be defined by the
J2EE spec, not anything specific to Tomcat.
Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.
Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.
And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.