Better handling of the "assets" route


#1

We have an app that could really use the “assets” route, and it doesn’t seem like a technical limitation unless I’m missing something…

Is there any way we can refine how we’re serving up a given route?

Right now assets is a protected route but couldn’t we just check the request header and do something similar in the ember-cli server? This would give us full access to any route, since we’d be relying more on the type of file being requested.

RewriteCond %{HTTP_ACCEPT}