On 6 Jul 2010, at 21:35, Giorgenes Gelatti wrote:On 6 July 2010 17:32, James Tucker <jftucker@gmail.com> wrote:
On 6 Jul 2010, at 17:57, Giorgenes Gelatti wrote:Hi,
It seems it hasn't been fixed yet. Is there any way around it?
I'm using ruby 1.9.1p378 (last stable version).I believe I added a workaround for this in rack. Try a newer version of rack.
I'm using rack 1.1.0 with gems 1.3.7 and the problem is still there :(
In what version is it supposed to be fixed?Just the repo version right now I believe.