Laurence Isla

All done! it's working correctly now :tada: Confirmed that both of the issues mentioned here are fixed https://github.com/PostgREST/postgrest/pull/3443#issuecomment-2103263050.

For PostgREST to return `Access-Control-Allow-Headers` you'll need to add the header `Access-Control-Request-Headers` in the CORS pre-flight request. It will include the header that you specify there in the list of...

> @laurenceisla Is there a way to control `Access-Control-Expose-Headers`? Not for now. The expose-headers are hard-coded here: https://github.com/PostgREST/postgrest/blob/b261abd5f543c1bdda4bc422ec1f13d542809cd3/src/PostgREST/Cors.hs#L36-L38 I'll update the title of this issue to include this header.

> @laurenceisla Looks like setting `response.headers` merges with existing values. 🎉 Cool, that's a nice workaround! Info on setting/reading headers can be found in the [Transaction settings section in the...

> What exactly do I need to do to deprecate the `server-timings-enabled` config? Should I just remove it from the codebase? Deprecating the config does not mean to remove it...

Since this will use the same host, then it would log this when the same port is used, right? ``` postgrest: Network.Socket.bind: resource busy (Address already in use) ``` It...

> Is there any real use-case that benefits from it? Mostly the case of to-many spreading/hoisting that I mentioned at the end. It's mostly to avoid confusion when using any...

> I guess my question is, whether the second example, without hoisting, is "sensible". I.e. would anybody use this? It would be sensible, for to-many relationships at least. My example...

> Should we maybe just put the part about the "old style GUC handling" in the respective branch as well? Yeah, that's better. Done that.

What's the exact request and response you're getting? An example using `curl -i ''` would be great to better pinpoint the issue. Perhaps this has to do with Media Type...