Handling directory routes that end both with and without a trailing slash

[cbebry]

I am using a route like follows, in order to serve static content in the public directory:

{ method: 'GET', path: '/{path*}', handler: { directory: { path: './public/', listing:true } } }

There is a subdirectory of public called cartography. Whenever I access the URL http://localhost/cartography/, everything works fine. However, when I access the URL http://localhost/cartography (without trailing slash) all of my relative URLs on the page become 404s because instead of looking for http://localhost/cartography/style.css, it serves http://localhost/style.css.

I admit to being spoiled by web servers like Apache/nginx, and I understand hapi may not necessarily be a replacement for Apache. I just happen to like hapi a lot.

My question is, what is the preferred way to handle this situation with the trailing slash? Is there a way to redirect users from the non-slash to the slash? Do I just not use relative URLs?

Thanks.

[iotaweb]

Hmm... I'm no Hapi expert, but I am not experiencing that problem. In my server options I have the following set:

var options = {
    ...
    files: {
        relativeTo: Path.join(__dirname, 'public')
    },
    ...
};

And in my routes, I have:

    // Add the routes (order does not matter)
    server.route([
        // Routes for index and partials
        { method: 'GET', path: '/', handler: getIndex },
        { method: 'GET', path: '/partials/{path}', handler: getPartial },
        // Routes for static resources, e.g. bower components, css, img, js
        { method: 'GET', path: '/components/{path*}', handler: { directory: { path: './components' } } },
        { method: 'GET', path: '/css/{path*}', handler: { directory: { path: './css' } } },
        { method: 'GET', path: '/img/{path*}', handler: { directory: { path: './img' } } },
        { method: 'GET', path: '/js/{path*}', handler: { directory: { path: './js' } } },
        // All remaining routes - redirect to index
        { method: 'GET', path: '/{path*}', handler: notFound }        
    ]);

I wonder if you're having the trailing slash issue because you've specified listing:true in your route?

[hueniverse]

I'm assuming you are navigating manually to http://localhost/cartography (e.g. you type it, not follow a link from http://localhost/)?

[cbebry]

@hueniverse I first noticed this when sharing the link as http://myhostname/cartography/ on Google Hangouts (with the slash), and the 'linkified' link did not glob the trailing slash. It does as well happen when the user types in the URL manually without the trailing slash. When the user uses the links from the http://myhostname/ page, everything behaves fine because I have control over that.

I understand that it is not the responsibility of the hapi team to be concerned with user error of incorrect typing or Google's very odd link globbing procedure. I'm bringing this up with hopes of finding a workaround or a suggested method so I can close up a potential hole in user experience of my application.