You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Paul Singleton <pa...@jbgb.com> on 2012/05/08 14:17:31 UTC
distinct HTTPS sites at distinct ports within same IP?
Is it feasible, under any Tomcat version, to offer two or more apps
via HTTPS (with own domains & certificates) on different port numbers
at a single IPv4 address?
I envisage name-based-virtual-server HTTP apps at port 80 which
302-redirect non-SSL requests to the corresponding port-specific HTTPS
app, on the optimistic assumption that no-one these days actually
types e.g.
https://my-secure-app.megacorp.com
just
my-secure-app.megacorp.com
Is this a really cheesy idea? have I missed something obvious?
Paul Singleton
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: distinct HTTPS sites at distinct ports within same IP?
Posted by Mark Thomas <ma...@apache.org>.
On 08/05/2012 13:17, Paul Singleton wrote:
> Is it feasible, under any Tomcat version, to offer two or more apps via
> HTTPS (with own domains & certificates) on different port numbers at a
> single IPv4 address?
Yes, under all currently supported versions.
>
> I envisage name-based-virtual-server HTTP apps at port 80 which
> 302-redirect non-SSL requests to the corresponding port-specific HTTPS
> app, on the optimistic assumption that no-one these days actually types
> e.g.
>
> https://my-secure-app.megacorp.com
I do...
> just
>
> my-secure-app.megacorp.com
>
> Is this a really cheesy idea? have I missed something obvious?
The port will appear in the URL and may or may not confuse some users.
I'd use httpd with SNI as a reverse proxy as a nicer solution.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org