On 18 Dec 2009, at 17:28, Stuart Watt wrote:
The documentation implies that a wildcard mapping is recommended
(although this is not supported by IIS5). I suspect the algorithm is
completely correct on IIS6/7 with a wildcard mapping.
Sounds like a reasonable conclusion.
Is this likely to require a patch to allow FastCGI to work with file
extension mapping? Shall I write one?
I recon so.
Yes, please do :)
There are tests for what the _fix_env stuff is doing for IIS already
here:
http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Runtime/5.80/trunk/t/aggregate/unit_core_engine_fixenv-iis6.t
More tests like this (failing) would be a great start, and there
really should be some tests like this:
http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Runtime/5.80/trunk/t/aggregate/unit_core_engine_cgi-prepare_path.t
for these FastCGI cases also (as that would test that Catalyst is
doing the right thing all the way through, not just that the mangling
was working.
If you fancy starting by grabbing the environment you're getting and
writing failing test cases that'd be _brilliant_ :_)
Feel free to mail them to the list, or come pester someone in
#catalyst-dev for a commit bit so you can add them directly yourself.
Thanks in advance.
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/
