Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document about authentication flow may be misleading? #173

Open
wdhongtw opened this issue Aug 20, 2021 · 0 comments
Open

Document about authentication flow may be misleading? #173

wdhongtw opened this issue Aug 20, 2021 · 0 comments

Comments

@wdhongtw
Copy link

The Authentication method says:

If you don't call it before calling one of the connection methods then it will be called for you on the first access.

And the Call method says

This will Authenticate if necessary, and re-authenticate if it receives a 401 error which means the token has expired

But if user create the connection object and use Call method directly, program will receive SIGSEGV,
because the conn.authLock member is not initialized yet. Other method like ObjectPut ObjectDelete also
suffer from this problem.

Although the sample code do call Authenticate after connection object construction. I thought the document may be
a little misleading. :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant