how to declare API routes properly? about angular-client-side-auth

[j8]

You should create a backend to provide an API and use AngularJS service + connect it to the routes using the resolve property. This is more question for stackoverflow instead of here.

[michaeljoser]

oups i probably phrased that question wrong... I am actually using angular-client-side-auth for my project... what i'm confused is why does /users give me the users in JSON format but the ones i declared in express server.js

app.get('/api/1/messages', function(req, res) { ...
...
...

those will result in Angular giving me a 404

[michaeljoser]

[SOLVED]

found this in route.js

    // User resource
    {
        path: '/users',
        httpMethod: 'GET',
        middleware: [UserCtrl.index],
        accessLevel: accessLevels.admin
    },

so i'm basically creating new resources/models/controllers to satisfy my API needs :)

[fnakstad]

Yep! You have to declare the the actual URL route on the server-side. If not it will be caught by a catchall route which will "delegate" the routing to the client-side Angular routing (from a server-side perspective it will just return the index site, which will cause Angular to check the route provided when it has been loaded). It works like this because I wanted pretty, "html5mode" url's on the client side :)