-
Notifications
You must be signed in to change notification settings - Fork 99
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
CORS issue when using custom api #282
Comments
I'm not able to reproduce this on the latest version 4.0.5. It's sending without errors for me. I'm running it by loading as an unpacked extension after running |
@alanhamlett I think you were able to figure out this issue with custom API url, because the latest (4.0.9) ffox version of the plugin sends heartbeats perfectly to a wakapi.dev instance. (I hate it too if somebody comments a closed issue, but I didn't want to reopen it, I just wanted you to know that this issue was solved. :) ) |
Thanks for updating, and verifying it's fixed! |
Sorry if it's necroposting here a bit, but on 4.0.9 running Firefox Nightly 134.0a1 (Oct 31), I'm getting empty POST requests & CORS errors from the OPTIONS requests. The OPTIONS request returns a 405 w/ error "CORS Missing Allow Origin". |
[XHR] [POST] https://wakapi.dev/api/users/current/heartbeats.bulk?api_key=(...)
I don't really know whether it is a problem with wakapi.dev server's config, or it can be fixed on client side, but I hope it can help you to understand the issue.
Originally posted by @Atko in #261 (comment)
The text was updated successfully, but these errors were encountered: