CORS policy issues #100
Description
We have some CORS policy issues on the API in the following scenarios:
- using authentication
- hitting old endpoints (before this change: feat: added prefix for both time and event based endpoints to make them distinct #93)
We also don't get 404 errors when hitting endpoints that do no exist.
Workarounds:
- When using authentication, it is actually preferable to use a backend not to expose the API token.
- front ends using the old endpoints should use the new ones for now