Dot in URL leads to 404

[lucaseverett]

If a URL contains a dot in the path (Eg. http://localhost:1234/foo.bar), 404 is returned.

I came across this issue while working on a SPA that passes names that may contain a dot in the URL. Using encodeURIComponent doesn't work on dots since they are valid in a URL path. As a workaround I manually performed a replace of the dots to encode them.

This is due to line 56 in Server.js

Currently the Server is treating all paths with a dot as a file extension, and rather than sending the index it is attempting to serve an asset with that name.

Would it be safe to change that line to verify that an asset by that name exists in the bundle, and if it doesn't then default to index?

[devArun01]

I got stuck with this issue for a while now. Will this be resolved?

[magcius]

Ow. I was relying on this behavior in my project to send me 404s for static data file requests that didn't exist.