Hi,
We have successfully got Tomcat running HTTPS and all our ebase apps are working well. However, this appears to prevent me getting in to the ebase Designer application which only seems to want to talk HTTP
Has anyone else been successful in getting Designer to connect when Tomcat is running HTTPS? Or am I missing something fundamental in my understanding?
Thanks,
Tomcat running HTTPS preventing ebase Designer access
Moderators: Jon, Steve, Ian, Dave
- Jez
- Ebase User
- Posts: 31
- Joined: Thu Aug 21, 2008 11:03 am
- Location: Hampshire County Council
Tomcat running HTTPS preventing ebase Designer access
0 x
--------------------------------------
Jez Hollinshead - Hampshire CC
Jez Hollinshead - Hampshire CC
-
- Moderator
- Posts: 1342
- Joined: Wed Sep 12, 2007 12:49 pm
-
- Ebase User
- Posts: 94
- Joined: Fri Sep 14, 2007 12:18 pm
- Location: The Netherlands
- Contact:
Re: Tomcat running HTTPS preventing ebase Designer access
I take it you are running Tomcat behind an HTTP-server.
You have at least the following options to this.
1. Allow connections through a specific port to Tomcat. In Tomcat that port has to be defined as an HTTP connector. You then connect the Ebase designer using the defined port that you have exposed to the internet.
2. Set-up a tunnel to the server and then use the tunnel to talk directly to Tomcat on Tomcats HTTP port (normally 3030).
3. If you have your domain redirecting to HTTPS and that is what is causing the problem, you could set up a sub-domain that does not redirect to HTTPS. http://www.mydomain.com redirects to https://www.mydomain.com and http://noredirect.mydomain.com stays on http://noredirect.mydomain.com for example.
You have at least the following options to this.
1. Allow connections through a specific port to Tomcat. In Tomcat that port has to be defined as an HTTP connector. You then connect the Ebase designer using the defined port that you have exposed to the internet.
2. Set-up a tunnel to the server and then use the tunnel to talk directly to Tomcat on Tomcats HTTP port (normally 3030).
3. If you have your domain redirecting to HTTPS and that is what is causing the problem, you could set up a sub-domain that does not redirect to HTTPS. http://www.mydomain.com redirects to https://www.mydomain.com and http://noredirect.mydomain.com stays on http://noredirect.mydomain.com for example.
0 x
Who is online
Users browsing this forum: No registered users and 106 guests