/foo and /foo/ are considered like two different routes server-side

[SachaG]

/foo and /foo/ are considered like two different routes server-side. Is that the intended behavior?

[tmeasday]

I think it's the same client side. It's not really intended I don't think.

On Monday, 8 July 2013 at 10:55 AM, Sacha Greif wrote:

/foo and /foo/ are considered like two different routes server-side. Is that the intended behavior?

—
Reply to this email directly or view it on GitHub (#106).

[SachaG]

Sorry, it's actually a little different from what I thought:

• When defining /foo, both /foo and /foo/ work.
• When defining /foo/, only /foo/ works.

Same behavior client and server-side. I guess I can live with that :)

[andreioprisan]

The /foo/ is meant to have parameters afterwards. i.e. /foo/:paramname
You can define different pages for /foo and /foo/:paramname, and check the value of paramname to redirect to /foo if undefined.
I would keep the current behavior because it seems more intuitive.