Re: Cookieless response

[kigster <kigster@gmail.com>]

I am having the same issue.  The reason is that Rails routing runs
last, after session and every other rack middleware.  Here is the
output of my "rake middleware" task:

use ActionDispatch::Static
use Rack::Lock
use ActiveSupport::Cache::Strategy::LocalCache
use Rack::Runtime
use Rails::Rack::Logger
use ActionDispatch::ShowExceptions
use ActionDispatch::RemoteIp
use Rack::Sendfile
use ActionDispatch::Callbacks
use ActiveRecord::ConnectionAdapters::ConnectionManagement
use ActiveRecord::QueryCache
use ActionDispatch::Cookies
use ActionDispatch::Session::CookieStore
use ActionDispatch::Flash
use ActionDispatch::ParamsParser
use Rack::MethodOverride
use ActionDispatch::Head
run Kigster::Application.routes

Because the routes run last, by the time the Rack/Sinatra application
is invoked, it ends up being inside of the Session::CookieStore which
wraps the response in the cookie.

With Rails Metal it was possible to bypass Rack completely, and build
routes that do not require Rails Router to get activated.  I just
tried doing "rails g metal" and my Rails3 project does not know this
generator.  So I am not sure how to create a pre-routing app handler
that would also bypass sessions.

Any help appreciated.

Konstantin

On Jul 16, 12:43 pm, Ryan  S <musicmanr...@gmail.com> 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