You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like we pass along an API user's token on the query string (via params), but I think this is deprecated and may stop working in late 2020, or even sooner during scheduled "brownouts".
It appears all of these calls are routed through our API wrapper, and ultimately forced through a single bottleneck in _WSWrapper._do_http. Maybe we could take this opportunity to examine params and move any auth_token value from there to an Authorization: token $TOKEN header added to _JSON_HEADERS.
The text was updated successfully, but these errors were encountered:
It looks like we pass along an API user's token on the query string (via
params
), but I think this is deprecated and may stop working in late 2020, or even sooner during scheduled "brownouts".It appears all of these calls are routed through our API wrapper, and ultimately forced through a single bottleneck in
_WSWrapper._do_http
. Maybe we could take this opportunity to examineparams
and move anyauth_token
value from there to anAuthorization: token $TOKEN
header added to_JSON_HEADERS
.The text was updated successfully, but these errors were encountered: