Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
allow_path_info and single / #8
If I have a component in the root of my site named
This URL does not match:
I think it should and path_info should be '/'.
referenced this issue
May 16, 2012
Just wanted to thank you for your Mason feedback and contributions, and apologize for the delay in responding to/adopting them. That is not the way I normally like to treat contributors...
I'm now finally unburying myself after a particularly busy season at work and working chronologically through my email backlog. Currently at January :), but moving forward.
On May 4, 2012, at 6:01 AM, Pedro Melo wrote:
It should certainly match. Not sure about path_info, in particular not sure whether trailing slashes should be automatically cleaned up from path_info. Should Mason in general treat path /foo/bar/ the same as /foo/bar?
Jonathan, no worries about the delays :)
Although I would personally choose to treat /foo/bar/ the same as /foo/bar, I also admit that it is because I'm biased to think in terms of mapping URLs to filesystems.
They are not the same URL, although years of automatic redirects by Apache and nginx from one to the other have trained us to think of them as the same.
I would keep path_info => '/' because it would allow each developer to decide if they are the same or not. Usually I like opinionated frameworks, but only if they let me choose my wrong way, if I really really need it.