Users might want to make requests against the database directly from a website. This however poses a problem for development and deployment as to the browser http://localhost:8181 is not the same as http://localhost:8282. We should change our responses to handle preflight checks from the browser and to respond with the correct headers so that requests in the browser work.

We had a user in Discord run into this issue and while using something like NGINX is the solution, that can be a bit operationally hard for a user to set up and run. We want to make sure the dev experience is quite smooth. We'll default to * for all the necessary headers as this mirrors what we would allow if a server made a request to the DB directly.