• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Rob Spoor
  • Henry Wong
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Carey Brown
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
Bartenders:
  • Frits Walraven
  • Himai Minh
  • Jj Roberts

Configure Tomcat for https without redirects?

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
 
Saloon Keeper
Posts: 23409
159
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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.
 
Karen Hartley
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Well, I'm accessing my page using the URL https://myapp.com:8443/app.jsp so I would *think* no redirects would need to happen - app.jsp is where the Firebase.js is loaded, and that is where the errors are showing up.  I can't think of a more direct way to go to the page, so the redirects must be something that Tomcat is doing under the covers, so to speak.
 
Tim Holloway
Saloon Keeper
Posts: 23409
159
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Since Firebase is itself doing web operations, I think you'll have to consider this to be something not quite right with your Firebase setup.

Unfortunately, I know nothing of Firebase, so I can't help there.
 
Just the other day, I was thinking ... about this tiny ad:
SKIP - a book about connecting industrious people with elderly land owners
https://coderanch.com/t/skip-book
reply
    Bookmark Topic Watch Topic
  • New Topic