Hi, On Fri, Jan 4, 2013 at 7:46 PM, Jonathan Swartz <swa...@pobox.com> wrote: > Oliver - I think you're right, this was a mistake. It was the result of > > https://github.com/jonswar/perl-mason/issues/8
Yup, it was my pull request, #11. > I'm not sure what the right behavior should be. For the sake of good SEO, you > generally want canonical urls and it's suboptimal to allow /foo/bar and > /foo/bar/ to map to the exact same thing. One of them should redirect to the > other. In the old Apache world, /foo/bar would redirect to /foo/bar/, but > these days it is much more common to have urls without trailing slashes. I think you comment here https://github.com/jonswar/perl-mason/issues/8#issuecomment-6903275 is what needs to be solved. > Feedback welcome. I agree, though, the current situation is very un-DWIM-ish. If you have foo.mc foo/index.mc or foo/dhandler.mc Which one should /foo/ match? If you only have foo.mc and no others, the redirect is a good solution, unless allow_path_info is set on foo.mc and then it should match without redirect with path_info eq '/'. But with foo/index.mc or foo/dhandler.mc present, the answer is not straightforward. I'm all for redirect (optional, on by default) if /foo/ is requested and only foo.mc exists *and* foo.mc has allow_path_info => 0. The other scenarios, not sure. Bye, -- Pedro Melo @pedromelo http://www.simplicidade.org/ http://about.me/melo xmpp:m...@simplicidade.org mailto:m...@simplicidade.org ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
