From: Rich Morin <rdm@cfcl.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Re: newby issue with rack-ssl gem
Date: Sun, 18 Dec 2016 10:04:44 -0800 (PST) [thread overview]
Message-ID: <0ca6dc1b-ee6d-4948-8f9f-e7ad6737d1d3@googlegroups.com> (raw)
In-Reply-To: <b1ee5da5-e269-4301-a329-676074943e47@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 425 bytes --]
Thanks for the detailed response! At the moment, I've taken rack-ssl out
of my code and simply tell folks to use the https url.
--
---
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 625 bytes --]
prev parent reply other threads:[~2016-12-18 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 0:32 newby issue with rack-ssl gem Rich Morin
2016-12-18 1:08 ` James Tucker
2016-12-18 1:42 ` Rich Morin
2016-12-18 1:49 ` James Tucker
2016-12-18 1:51 ` Rich Morin
2016-12-18 7:01 ` James Tucker
2016-12-18 18:04 ` Rich Morin [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-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=0ca6dc1b-ee6d-4948-8f9f-e7ad6737d1d3@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).