Re: Cookieless response

[Konstantin Haase <k.haase@finn.de>]

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