-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add missing headers and user-name header rotation #43
Conversation
Fix #42 |
Sorry for being so inactive the past couple weeks - lots going on! The changes LGTM, thanks. I made a couple more upstream; like using base32 and ensuring the clients / contexts are passed around correctly. Should we merge them here? I can confirm that the client works, albeit with major rate limiting applied. |
Yes please! It's your PR anyway- please feel free to amend or open new one. Btw., do you intend to keep maintaining your repo or wouldn't it be easier to do all evolution here? |
ping @uhthomas seem we should get this closed before 1.0? |
@uhthomas I've merged your base32 changes but didn't take over returning the context as I didn't understand why that's needed. |
4d92d2e
to
9480e6c
Compare
@bogosj Rebased. Shall we get this in? |
* Use provided context client for login * Use tesla transport for authorization and client * wip * wip * wip * Merge remaining changes * Fix linter errors * Clarify code
This does not solve the current login issues but exposes the login request flow using a logging http client.
Note: might also make sense to only update the transport: https://github.com/uhthomas/tesla/compare/f00d0e07a2b61907751647920f5b7c1f8197c07a..1caf33b692d9258ef27505b335ee3aa8869c1e8d#diff-c52daedaeda258db15ec11d57bbf299412a20328f6cd026980ef07f01960dd3aR25