From: Eric Wong <e@80x24.org>
To: yahns-public@yhbt.net, kcar-public@bogomips.org
Subject: Re: yahns will use kcar as a request parser
Date: Wed, 19 Apr 2017 00:13:49 +0000 [thread overview]
Message-ID: <20170419001349.GA3474@starla> (raw)
In-Reply-To: <20170408003732.GA5176@starla>
The current parser used by yahns interprets X-Forwarded-Proto
and X-Forwarded-Ssl headers to set rack.url_scheme in the
rack request env.
Since these are non-standard headers, I think we can safely drop
support for them in yahns. Neither passenger, puma, nor thin
seem to respect them when setting rack.url_scheme, either...
Anyways, these headers are used by Rack::Request,
and RFC 7239 ("Forwarded" header) was standardized in 2014,
so maybe some people would rather use that instead, too...
prev parent reply other threads:[~2017-04-19 0:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 0:37 yahns will use kcar as a request parser Eric Wong
2017-04-19 0:13 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/yahns/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170419001349.GA3474@starla \
--to=e@80x24.org \
--cc=kcar-public@bogomips.org \
--cc=yahns-public@yhbt.net \
/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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/yahns.git/
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).