http.ListenAndServe requires two arguments, the second one can be nil,
but must be present. https://golang.org/pkg/net/http/#ListenAndServe
Omitting it, even in just documention code snippets like ths one,
might confuse people just learning (like myself).
http.ListenAndServe requires two arguments, the second one can be nil,
but must be present. https://golang.org/pkg/net/http/#ListenAndServe
Omitting it, even in just documention code snippets like ths one,
might confuse people just learning (like myself).
This reverts commit 3b11e039dc802bfc865cd2e515583e9b0911aaf0, reversing
changes made to 586415a7db9d2b1538cd2c05ca2dbbce0ee9cc62.
This merge actually caused the tests to fail. After digging in I decided
that the documentation is good enough as a test on creation of Authboss
is not possible with the current API. And this being only in the
register module was kind of a code smell.
This reverts commit 3b11e039dc802bfc865cd2e515583e9b0911aaf0, reversing
changes made to 586415a7db9d2b1538cd2c05ca2dbbce0ee9cc62.
This merge actually caused the tests to fail. After digging in I decided
that the documentation is good enough as a test on creation of Authboss
is not possible with the current API. And this being only in the
register module was kind of a code smell.
- Fix#79
- Rename event EventGet to EventGetUser
- Remove double DB fetch
- Add new event callpoint: After(EventGetUser) for things that need to
check that the user is ABLE to be gotten after it's fetched from the
DB. That is before returning to the web app, ensure that the user is
valid from a confirmation/lock etc point of view.
- Add test to make sure all the events are firing in CurrentUser()
- When authboss routes are accessed it goes through a check to see if
they're logged in and if they need to actually visit this route. If
the user was not found (despite having a session cookie) it would 500,
and now it simply removes the bad cookie.
- Fix#75
