Re: webrick, ssl and non-ssl on the same port
- From: "Michal Suchanek" <hramrach@xxxxxxxxxx>
- Date: Wed, 16 Aug 2006 02:51:20 +0900
On 8/10/06, Francis Cianfrocca <garbagecat10@xxxxxxxxx> wrote:
On 8/10/06, Pavel Smerk <smerk@xxxxxxxxxx> wrote:
> Hello all,
>
> I have sslized webrick server, but I'd like to have some parts of server
> accessible even without ssl. I've tried to search web and groups, but
> I haven't found anything --- any suggestions, how to get ssl and nonssl
> servlets on the same port?
>
> Thanks in advance,
>
> P.
>
>
what I think you're proposing is not usually done for web sites. Do
you want to open a server port and have it automatically detect an
SSL/TLS client-hello so you can do an SSL handshake if present, and
simply serve the connection with no encryption otherwise? If you do
that, then how do you ensure that people will use encryption on the
sensitive pages? It's a lot of additional logic to make that happen.
Just use two ports.
The page is either available through http or https - these are two
different URLs. So the request should get to the right type of
service.
Of course it is simpler to use two ports (and it is the default
anyway, you would have to use a port number with either http or https
to get them use the same port). But it is an interesting idea
nontheless.
Thanks
Michal
.
- References:
- webrick, ssl and non-ssl on the same port
- From: Pavel Smerk
- Re: webrick, ssl and non-ssl on the same port
- From: Francis Cianfrocca
- webrick, ssl and non-ssl on the same port
- Prev by Date: Re: binary extension compatibility on OS X
- Next by Date: Re: _ in URI subdomain problem
- Previous by thread: Re: webrick, ssl and non-ssl on the same port
- Next by thread: rBATIS - alternative ORM for Ruby / Rails (via Martin Fowler)
- Index(es):
Relevant Pages
|
