requiresLogin in authorization.js redirects to dead location

[linnovate]

requiresLogin in authorization.js redirects to dead location

[geekyme]

why is this closed? I just cloned the repository and simulated the problem by deleting session cookies in the browser right before I create an article.
This results in the above middleware catching and making the call to "return res.redirect('/login')). However, the browser does not do a proper redirect to /login as expected.

Browser redirected to http://localhost:3000/#!/articles/undefined

the is the stack trace:

 
CastError: Cast to ObjectId failed for value "undefined" at path "_id"
    at ObjectId.cast (C:\Users\shawnlim\Documents\Websites\angularjs\mean\node_m
odules\mongoose\lib\schema\objectid.js:116:13)
    at ObjectId.castForQuery (C:\Users\shawnlim\Documents\Websites\angularjs\mea
n\node_modules\mongoose\lib\schema\objectid.js:165:17)
    at Query.cast (C:\Users\shawnlim\Documents\Websites\angularjs\mean\node_modu
les\mongoose\lib\query.js:412:32)
    at Query.findOne (C:\Users\shawnlim\Documents\Websites\angularjs\mean\node_m
odules\mongoose\lib\query.js:1762:10)
    at Query.exec (C:\Users\shawnlim\Documents\Websites\angularjs\mean\node_modu
les\mongoose\lib\query.js:171:16)
    at Function.ArticleSchema.statics.load (C:\Users\shawnlim\Documents\Websites
\angularjs\mean\app\models\article.js:41:29)
    at exports.article (C:\Users\shawnlim\Documents\Websites\angularjs\mean\app\
controllers\articles.js:14:13)
    at paramCallback (C:\Users\shawnlim\Documents\Websites\angularjs\mean\node_m
odules\express\lib\router\index.js:151:7)
    at param (C:\Users\shawnlim\Documents\Websites\angularjs\mean\node_modules\e
xpress\lib\router\index.js:133:11)
    at pass (C:\Users\shawnlim\Documents\Websites\angularjs\mean\node_modules\ex
press\lib\router\index.js:145:5)

how can the problem be solved?

[amoshaviv]

hey @geekyme, it was close because it was duplicate, i now added the duplicate label, i just pushed a fix to the authentication middleware that solves the entire issue.
The seed project didn't include angular so the authentication middleware behaved differently of what it should have.

[geekyme]

i just tried it, receiving a PUT http://localhost:3000/articles/522d7e1fc31738382f000004 401 (Unauthorized) in browser console log now when I deleted the session cookie.

Do I have to do a redirect to login page on the client side?