I don't like this approach to routing - REST is the key while designing routes.

What is this route about? 
The users route -> a singular resource has to be chosen: avatar

What operations exist?
new - POST to /avatar
get is - GET /avatar
delete it - DELETE /avatar

We might want to add a prefix to the route - let's see.

In addition I'd like to see all code regarding avatar in one place e.g. /lib/avatar (with exception of the public stuff of course :wink:)