unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@yhbt.net>
To: Keven Sticher <ksticher@gmail.com>
Cc: unicorn-public@yhbt.net
Subject: Re: Can Unicorn utilize HTTPS?
Date: Thu, 6 Aug 2020 21:54:57 +0000	[thread overview]
Message-ID: <20200806215303.GA7045@dcvr> (raw)
In-Reply-To: <8B1A0D8D-04AC-4063-95A6-F73E1F041419@gmail.com>

Keven Sticher <ksticher@gmail.com> wrote:
> Going through some internal debate, and if end to end encryption is required through all layers, does Unicorn handle TLS, SSL, HTTPS?

Nope.  It's only intended to talk to nginx over a Unix domain
socket on the same host, or nginx on a fast private LAN.  Having
something like varnish or haproxy in between nginx and unicorn
is fine, too, but they must either be on the same host or fast

It fails horribly (by design :>) when talking to the open Internet
or any high-latency clients.

> Thank you for your response.

no problem :>

      reply	other threads:[~2020-08-06 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 21:46 Can Unicorn utilize HTTPS? Keven Sticher
2020-08-06 21:54 ` Eric Wong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200806215303.GA7045@dcvr \
    --to=e@yhbt.net \
    --cc=ksticher@gmail.com \
    --cc=unicorn-public@yhbt.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).