From: Simon Menke <simon.menke@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: SSL Peer Certificate in the environment.
Date: Thu, 6 Jan 2011 07:15:48 -0800 (PST) [thread overview]
Message-ID: <b603991d-8fc8-4820-b5fb-a28588cd23f6@l8g2000yqh.googlegroups.com> (raw)
Hi,
After looking around for a while I haven't found a standard env key
for the SSL/TLS peer certificate.
So I would like to suggest { 'rack.ssl.peer_cert' => String }. The
String value should be a PEM encoded certificate.
It seems natural to have a standard env key as it is a standard HTTP
feature.
reply other threads:[~2011-01-06 15:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b603991d-8fc8-4820-b5fb-a28588cd23f6@l8g2000yqh.googlegroups.com \
--to=rack-devel@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
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).