From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.49.85.105 with SMTP id g9csp291543qez; Tue, 22 Jan 2013 16:27:45 -0800 (PST) Return-Path: Received-SPF: pass (google.com: domain of rack-devel+bncBDKJRJVBSMLBBAG57SDQKGQEASV5GDA@googlegroups.com designates 10.50.37.242 as permitted sender) client-ip=10.50.37.242 Authentication-Results: mr.google.com; spf=pass (google.com: domain of rack-devel+bncBDKJRJVBSMLBBAG57SDQKGQEASV5GDA@googlegroups.com designates 10.50.37.242 as permitted sender) smtp.mail=rack-devel+bncBDKJRJVBSMLBBAG57SDQKGQEASV5GDA@googlegroups.com; dkim=pass header.i=@googlegroups.com X-Received: from mr.google.com ([10.50.37.242]) by 10.50.37.242 with SMTP id b18mr16659547igk.6.1358900865247 (num_hops = 1); Tue, 22 Jan 2013 16:27:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:x-received:received-spf:date:from :to:subject:message-id:references:mime-version:in-reply-to :user-agent:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:x-google-group-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type:content-disposition; bh=/prOhv1q9RUCLDwEed2JhPstZPv8ZoFCFs2Djt8cgHg=; b=MGmMQamT5B2lk292ZYq2uR4QFuORt500RkyqbIaet2bNTHLyyXl2MpUdQWJaCL+JjH Rs+bM1XugPLs4REMpNmvbgHiy6LzaF1umB4udGUxF6o5ATAuhiItBAbr2fAoSYjcTHt7 jv/A5RfiqmcjZG8hcUlkdzCwGjifItSqdqo/n60haNM/JTnwgVw8Jb1O12wN3wl/OJNR pEymuIxuv/9Yy/nqpCfCTaACNiQCDbU7YWvch5uypPQk0MGVIgZ1MQPQtzWnsRzmgpcD z93yw3tUKA4bN6RFVwhWPeQ80TmjBr8HiYHuILfxYUaC7mwwV3xmjBlToak/6ZpeNQwp Ys0g== X-Received: by 10.50.37.242 with SMTP id b18mr4737083igk.6.1358900864788; Tue, 22 Jan 2013 16:27:44 -0800 (PST) X-BeenThere: rack-devel@googlegroups.com Received: by 10.50.193.134 with SMTP id ho6ls3531894igc.23.canary; Tue, 22 Jan 2013 16:27:44 -0800 (PST) X-Received: by 10.66.86.138 with SMTP id p10mr2465572paz.14.1358900864308; Tue, 22 Jan 2013 16:27:44 -0800 (PST) X-Received: by 10.66.86.138 with SMTP id p10mr2465571paz.14.1358900864297; Tue, 22 Jan 2013 16:27:44 -0800 (PST) Received: from dcvr.yhbt.net (dcvr.yhbt.net. [64.71.152.64]) by gmr-mx.google.com with ESMTP id n8si3483633paz.2.2013.01.22.16.27.44; Tue, 22 Jan 2013 16:27:44 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of normalperson@yhbt.net designates 64.71.152.64 as permitted sender) client-ip=64.71.152.64; Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id E32061F6E1; Wed, 23 Jan 2013 00:27:43 +0000 (UTC) Date: Wed, 23 Jan 2013 00:27:43 +0000 From: Eric Wong To: rack-devel@googlegroups.com Subject: Re: [SEC][ANN] Rack 1.5.0, a modular Ruby webserver interface Message-ID: <20130123002743.GA8819@dcvr.yhbt.net> References: <50fe43c2.68dc440a.126d.ffffe987@mx.google.com> <20130122100802.GA28585@dcvr.yhbt.net> MIME-Version: 1.0 In-Reply-To: <20130122100802.GA28585@dcvr.yhbt.net> User-Agent: Mutt/1.5.20 (2009-06-14) X-Original-Sender: normalperson@yhbt.net X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of normalperson@yhbt.net designates 64.71.152.64 as permitted sender) smtp.mail=normalperson@yhbt.net Reply-To: rack-devel@googlegroups.com Precedence: list Mailing-list: list rack-devel@googlegroups.com; contact rack-devel+owners@googlegroups.com List-ID: X-Google-Group-Id: 486215384060 List-Post: , List-Help: , List-Archive: Sender: rack-devel@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=us-ascii Content-Disposition: inline (culling Cc:) Eric Wong wrote: > jftucker@gmail.com wrote: > > Additonally, SPEC has been updated in several areas and is now at 1,2. > > SPEC still says this: > > rack.version:: The Array [1,1], representing this version of Rack. > > I take it 1,2-compliant servers should set [1,2] there instead? > > > A new SPEC section was introduced that provides two server-optional IO hijacking > > APIs. Further information on these APIs will be made available by the community > > in good time. In the mean time, some information can be found in the original > > pull request: https://github.com/rack/rack/pull/481 So once a connection is hijacked, there's no un-hijacking, correct? The server needs to completely ignore the normal Rack response (I also just posted a Rack::Lint patch here to that effect) > Cool. Should be easy for unicorn, and some configurations of > Rainbows!/zbatery. I'm setting env["rack.version"] to [1,2] in my unicorn hijack branch. Would greatly appreciate ACK/NACK on whether this is the way to go. Original patch to implement hijack: http://mid.gmane.org/20130122114943.GA8455@dcvr.yhbt.net Followup to ignore responses for hijacked requests: http://mid.gmane.org/20130122235728.GA8717@dcvr.yhbt.net