Samuel Williams

We could consider using `symbolize_names` or similar when using JSON. I think it's less surprising in most cases.

Thanks for persisting with this, I'll review it today.

That seems reasonable to me, but I don't fully grok the implications. Do you mind submitting a PR? Then we can discuss the specifics.

> It is perfectly valid to do this for localhost Is there any other evidence (library implementation, framework, documentation) to support this assertion? It would be extremely helpful to understand...

Just for reference, I assume we are talking about: > A cookie with the Secure attribute is only sent to the server with an encrypted request over the HTTPS protocol....

Does the JSON data get encoded as the raw value of the header? If so, the only solution would be to base64 (or url encode) it, e.g. emoji -> JSON...

I just wanted to throw falcon at it and see how it compared but I also want to use async-postgres so might require some hacking.

`async-postgres` is a monkey patch on top of `pg` so in theory it's completely compatible, it's just a matter of loading it (i.e. `require 'async/postgres' if defined? Falcon`).

Rather than using docker, for my own benchmark, I used `systemd-machinectl` and `pacman`: https://github.com/socketry/falcon-benchmark While it is a bit more platform specific than I'd like, it's super simple to deploy...

Sorry, I didn't really make any useful statement. What about this: it sounds like you already have things set up on your end, do you just want to try it...