Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

There may be problems with best ingest #81

Open
tyiki-badwell opened this issue Feb 2, 2019 · 0 comments
Open

There may be problems with best ingest #81

tyiki-badwell opened this issue Feb 2, 2019 · 0 comments

Comments

@tyiki-badwell
Copy link
Contributor

When we specify auto for ingest_hostname, the API goes to access
https://mixer.com/api/v1/ingests/best
and the following message is returned in the HTTP header.

x-warning: Calls must be updated to include a Client-ID header by May 21st. See more: https://aka.ms/MixerDevIdentification

When it is unknown when May 21st, we need to know if we have to respond.

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

No branches or pull requests

1 participant