On Thu, May 28, 2009 at 8:15 PM, Johan Sørensen <[email protected]> wrote: > The motive behind this, apart from needless Set-Cookie headers
FWIW, a lot of people like sending Set-Cookie headers on every response, because it ensures you get punched through caches. Certainly, a significant number of apps don't need that, but it's something to bear in mind - I think we would not want to quietly turn off (most) Set-Cookie headers in an upgrade, IMHO it would need to be an option; otherwise people will upgrade and wonder why they're suddenly having odd caching problems from crappy proxy servers. (Of course, HTTP itself has proper ways to deal with that - the varies headers etc.) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
