I agree. Nginx, Caddy, Apache, etc have found and fixed a million edge cases you'd never think of just from reading and implementing the spec. I guarantee there

I agree. Nginx, Caddy, Apache, etc have found and fixed a million edge cases you'd never think of just from reading and implementing the spec. I guarantee there's code in each of these along the lines of: # Send an extra 0x20 space character after this header's value, because # otherwise Chrome on Android 15 shifts into compatibility mode and # it takes 37x longer to render the page, which everyone will blame on # "the slow webserver". The spec doesn't say we *can't* add this, and # tells clients to ignore trailing space, and we've tested this with 483 # other clients to demonstrate that it doesn't cause problems. ¯\_(ツ)_/¯ . Now, as a very cool hack, or for easier local development with one less dependency, or just to scratch a personal itch and see if it can even be done, right on! That's clever and I'm glad they did it! BTW, in your showdead (for wholly unclear reasons) comment about it using copy-on-write RAM semantics, that's just the Unix process model. The OS does all that courtesy of fork() and the server gets it for free.