Thanks.
Can anybody confirm whether this change doesn't break Sinatra on Apache?
--
Phusion | The Computer Science Company
Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)
>
> On Sun, Apr 19, 2009 at 1:27 AM, Tim Carey-Smith <g...@spork.in> wrote:
>>
>> I have fixed the problem on my fork.
>>
>> http://github.com/halorgium/passenger/commit/b8b360ea1d960e965fe7a7fec3df9a36aa04e13b
>> http://github.com/halorgium/passenger/commit/6d64144b1c57e5b7788537fe07dca1f3e9e7c388
>>
>> Two commits cause I almost failed miserably :)
>>
>> Can someone check that I'm not doing something insanely stupid?
>>
>> Thanks Dylan for the split line.
>
> Thanks.
>
> Can anybody confirm whether this change doesn't break Sinatra on
> Apache?
The only thing which this changes is that it will overwrite the
PATH_INFO which apache provides.
Maybe it should change from:
> headers["PATH_INFO"] = headers["REQUEST_URI"].split("?", 2).first
to:
> headers["PATH_INFO"] ||= headers["REQUEST_URI"].split("?", 2).first
So it'll keep the existing value.
Ciao,
Tim
Not yet, we haven't had the time to review it yet but it's on the top
of our todo list.
The problem has been fixed in git now.