From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.140.199.13 with SMTP id w13cs117375rvf; Mon, 19 Oct 2009 20:21:46 -0700 (PDT) Return-Path: Received-SPF: pass (google.com: domain of grbounce-ceibQwUAAAB4YPBqaDIjI2bFOCxyyh3G=chneukirchen=gmail.com@googlegroups.com designates 10.220.89.218 as permitted sender) client-ip=10.220.89.218; Authentication-Results: mr.google.com; spf=pass (google.com: domain of grbounce-ceibQwUAAAB4YPBqaDIjI2bFOCxyyh3G=chneukirchen=gmail.com@googlegroups.com designates 10.220.89.218 as permitted sender) smtp.mail=grbounce-ceibQwUAAAB4YPBqaDIjI2bFOCxyyh3G=chneukirchen=gmail.com@googlegroups.com; dkim=pass header.i=grbounce-ceibQwUAAAB4YPBqaDIjI2bFOCxyyh3G=chneukirchen=gmail.com@googlegroups.com Received: from mr.google.com ([10.220.89.218]) by 10.220.89.218 with SMTP id f26mr7949277vcm.19.1256008905531 (num_hops = 1); Mon, 19 Oct 2009 20:21:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:received:received:x-sender:x-apparently-to :mime-version:content-type:received:date:x-ip:user-agent :x-http-useragent:message-id:subject:from:to:x-google-approved :reply-to:sender:precedence:x-google-loop:mailing-list:list-id :list-post:list-help:list-unsubscribe:x-beenthere-env:x-beenthere; bh=kxzGIJ4nSLMW/n8OY/ZIShX2zfEsk1L9FbePbhoqkoU=; b=ukMCXCzB5nIq416E+yf0Nnry2yh6znu4wE5dPzQ3aMEHYpFn3u8Xtuhzk27PUlbjV6 x01WKHcRCiDCH+woqq5eIVbgaevT4NtD5OLFn3flHvzXPXnxsknL59EUevJhkx2KjSop W/o3s5BfT8r/4bo4dcK7S1ve3nRj5tY6Pzx8Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-sender:x-apparently-to:mime-version:content-type:date:x-ip :user-agent:x-http-useragent:message-id:subject:from:to :x-google-approved:reply-to:sender:precedence:x-google-loop :mailing-list:list-id:list-post:list-help:list-unsubscribe :x-beenthere-env:x-beenthere; b=zCmUia5QEjhj0YBjjO+3jzcC66op1oxVY/1BmBX4D3+JJKAEb8+lEOtQA/Kj7T3Fm+ 8Gmvrcwg/QA4xKLDQdlZPQlbbE79H3co6XRhroKEi0soqsW60O5y+paKIHb97p7DU18O FQATVZAVJVpr5M1Lou3GIL6EJ5eWkMWCytuRI= Received: by 10.220.89.218 with SMTP id f26mr752761vcm.19.1256008905431; Mon, 19 Oct 2009 20:21:45 -0700 (PDT) Received: by 10.176.181.37 with SMTP id d37gr1707yqf.0; Mon, 19 Oct 2009 20:21:39 -0700 (PDT) X-Sender: julien.genestoux@gmail.com X-Apparently-To: rack-devel@googlegroups.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Received: by 10.150.44.14 with SMTP id r14mr636031ybr.8.1256002320479; Mon, 19 Oct 2009 18:32:00 -0700 (PDT) Date: Mon, 19 Oct 2009 18:32:00 -0700 (PDT) X-IP: 64.81.241.91 User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_1; en-us) AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9,gzip(gfe),gzip(gfe) Message-ID: <72080a3b-08b6-4e21-8071-ffac95a8e531@e18g2000vbe.googlegroups.com> Subject: Extract several POST Params with the same name From: Julien To: Rack Development X-Google-Approved: m.fellinger@gmail.com via web at 2009-10-20 03:21:37 Reply-To: rack-devel@googlegroups.com Sender: rack-devel@googlegroups.com Precedence: bulk X-Google-Loop: groups Mailing-List: list rack-devel@googlegroups.com; contact rack-devel+owner@googlegroups.com List-Id: List-Post: List-Help: List-Unsubscribe: , X-BeenThere-Env: rack-devel@googlegroups.com X-BeenThere: rack-devel@googlegroups.com Hi everyone, In the context of creating a Hub for PubSubHubbub using Rails, it seems that our app must be able to handle POST queries with multiple occurences of params with the same name. (Please see this disucssion : http://groups.google.com/group/pubsubhubbub/browse_thread/thread/bc971f0a4a99c446) Right now, when I perform a call to my Rails app (which uses Rack) with 2 params hub.mode having different values: hub.mode=subscribe&hub.topic=http&hub.callback=http2&hub.verify=sync&hub.verify=async Then, it seems that my app only sees that "last value", and params ["hub.verify"] = async. I am not sure this is Rack's responsibility, but whil debugging I was able to see that Rack had access to the right data in env ["rack.input"] and was able to "hack" that by forcing params ["hub.verify"] to be an arary containing both values. Do you think that the HTTP params parser could be "fixed" to work with that? Thanks,