Our Rails3 (beta4) application had one route mapped in config/routes to a Sinatra app, by means of the following route: match '/foo', :to => EndPointApp, :as => :endpoint The route was being defined to run as a Sinatra Application require 'sinatra' class EndPointApp < Sinatra::Application post '/foo' do ... end end This was working mostly fine, but it was returning Set-Cookie header with the standard Rails sessions cookie, which in this case was preventing the client of this endpoint from successfully interpreting the result. As I could do nothing about the client side, I had to remove Set-Cookie from the headers, but only for this end-point and obviously not from the entire app. This proved to be somewhat more complicated than I had hoped, so let me share the solution here in hopes it might save someone else an hour or two. First, I ran "rake middleware" and observed the following Rack stack: use ActionDispatch::Static use Rack::Lo
Tech ramblings by Konstantin Gredeskoul