From: Yehuda Katz <wycats@gmail.com>
To: rack-devel <rack-devel@googlegroups.com>
Subject: Re: Should we continue to support session in params?
Date: Sun, 3 Oct 2010 10:59:16 -0700 [thread overview]
Message-ID: <AANLkTimpY6O3Wm31qNWU8PwsR5MryUyDcZ6LRLiOdnx_@mail.gmail.com> (raw)
In-Reply-To: <979DB45B-64D5-40F9-9592-F0CC0126E007@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
Unfortunately, this probably exists to support Flash file uploads, which
can't pass cookies due to an ancient, still unfixed API bug.
Yehuda Katz
Architect | Strobe
(ph) 718.877.1325
On Sun, Oct 3, 2010 at 10:03 AM, James Tucker <jftucker@gmail.com> wrote:
> There's an option in the sessions infrastructure to support sessions via
> params. It's untested anywhere except in the memcache session specs. I'd
> like to remove it as it's nothing but an optional security hole. I can't
> imagine anyone using this for anything sane, but I'm checking here in case
> I'm wrong.
[-- Attachment #2: Type: text/html, Size: 1000 bytes --]
next prev parent reply other threads:[~2010-10-03 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 17:03 Should we continue to support session in params? James Tucker
2010-10-03 17:59 ` Yehuda Katz [this message]
2010-10-03 18:07 ` James Tucker
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=AANLkTimpY6O3Wm31qNWU8PwsR5MryUyDcZ6LRLiOdnx_@mail.gmail.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).