Vanilla

This appears to still be an issue on elasticsearch-py version 8.5.0 and elasticsearch version 8.5.3. The misleading error message cost us quite some time re-evaluating our elasticsearch configuration. Would be...

Also having this issue in a React environment. Works fine in regular node.js with the same function call. Also works when setting up the scraper with a proxy, i.e., this...

No other error messages in the console. I don't really know enough about the auth flow to tell what exactly is going on, but looks like a "flow_token" is successfully...

So from what I can tell, these are the headers being set by Node.js (defined in auth-user.js, executeFlowTask(data)) ```js async executeFlowTask(data) { const onboardingTaskUrl = 'https://api.twitter.com/1.1/onboarding/task.json'; const token = this.guestToken;...