On 18 Dec 2009, at 19:07, William Wueppelmann wrote:
Thanks, but I am already using 5.80016.
My suspicion is that the problem actually lies somewhere between
apache and fastcgi, but I really don't know. A request for '/' gets
mapped to '/foo/bar' and processed correctly, but everything else
just gets passed through as-is.
ok, can you hack C::Engine::FastCGI, and use data::dumper or something
to dump what %ENV contains when things are getting it wrong, and also
get the debug dump screen's dumped Catalyst::Request object?
That's enough info to be able to work out what's being presented to
Catalyst by FCGI, and what Catalyst is doing with it..
And should allow someone to write a failing test case (like this: http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Runtime/5.80/trunk/t/aggregate/unit_core_engine_cgi-prepare_path.t)
, which we can then fix..
If you fancy jumping directly to patching that test right there to
check your scenario, that'd be even better :)
Please feel free to appear in #catalyst-dev and pester people by
nopasteing dumps, failing tests etc and someone will hand you a commit
bit.
Apologies, at a guess this is further fallout from the changes to be
able to correctly deal with uri encoded slashes in the request in
5.80015 :(
Cheers
t0m
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
