From: "José Valim" <jose.valim@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Re: Cookieless response
Date: Mon, 19 Jul 2010 11:32:05 -0700 (PDT) [thread overview]
Message-ID: <462a37ee-2066-4848-97c0-b0fe16a56f9b@q35g2000yqn.googlegroups.com> (raw)
In-Reply-To: <ac9f7337-24b3-49fe-b51c-49d13a94ea50@g19g2000yqc.googlegroups.com>
Latest Rails (git master) should lazily create the session.
On Jul 16, 10:02 pm, Ryan S <musicmanr...@gmail.com> wrote:
> Yeah, I don't understand the way the stack works very well when it
> comes to Rails and Rack. It was worth a shot.
>
> On Jul 16, 2:47 pm, Konstantin Haase <k.ha...@finn.de> wrote:
>
>
>
> > I think it's rails placing its middleware for handling the session in front of your app (unless there is a enable(:session)) in your app. No clue where to fix this.
>
> > Konstantin
>
> > On Jul 16, 2010, at 21:43 , Ryan S wrote:
>
> > > So let's say I just have a simple rack app
>
> > > class SimpleApp
> > > def self.call(env)
> > > [200, {}, "I don't want no cookies!"] #I am a grammarian
> > > end
> > > end
>
> > > A rails route:
>
> > > root :to => SimpleApp
>
> > > Where do I add this middleware that suppresses the cookie from the
> > > response? This may not even be possible to just suppress a cookie for
> > > one response as the domain as a whole uses cookies so this may just be
> > > my lack of understanding here.
>
> > > On Jul 16, 2:23 pm, Konstantin Haase <k.ha...@finn.de> wrote:
> > >> On Jul 16, 2010, at 21:11 , Ryan S wrote:
>
> > >>> So I am using a basic rack app in my rails 3 project to serve a
> > >>> javascript file from a git repo and will pull different versions of
> > >>> the file based on a query param.
>
> > >>> I notice in the headers that there is a 'Set-Cookie ' cookie header. I
> > >>> can't seem to get that to go away. Is it possible to have a response
> > >>> without a cookie?
>
> > >> Make sure you have no session middleware in your stack.
>
> > >> Konstantin
next prev parent reply other threads:[~2010-07-20 1:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 19:11 Cookieless response Ryan S
2010-07-16 19:23 ` Konstantin Haase
2010-07-16 19:43 ` Ryan S
2010-07-16 19:47 ` Konstantin Haase
2010-07-16 20:02 ` Ryan S
2010-07-19 18:32 ` José Valim [this message]
2010-07-26 21:46 ` kigster
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=462a37ee-2066-4848-97c0-b0fe16a56f9b@q35g2000yqn.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).