Define behavior for consecutive '/'s in requests

[jnichols-git]

Under RFC 2396, static//route is a valid URI/request path, which would literally evaluate to 'static', '', 'route' as parts. However, it doesn't specifically define what should happen when someone makes a request like this. Modern OSs treat consecutive slashes as a single slash, ex. static////////route becomes static/route, so I would like to take that approach.

I'm marking this as a bug because I didn't define or test this behavior originally. I'll take this on after CORS handling if nobody else steps in.

[jnichols-git]

Tacking trailing slashes onto this, routes ending in / should be treated as if they don't.

[jnichols-git]

Closed by #38