Kraken root doesn't accept OPTIONS, breaks CORS

Kraken root returns 400 bad request for OPTIONS, which is sent as part of a cross-origin XHR breaking CORS on the endpoint entirely. This breaks getting the username of a user without user_read in a web application, unless jsonp is used.

Edit: only happens when Client-ID is sent via header.

Thanks for the heads up! I’ll ask the team about it.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

@3ventic This should’ve been fixed. Forgot to follow up before Christmas break. Let me know if it is still an issue!

1 Like