I think we should probably consider having the server return Not Modified when provided with a matching If-None-Match as acceptance criteria here.
I guess ETag is only helpful if the httpd knows how to handle it, though :P
Not that cksum is expensive, but it seems a bit wasteful to do it every request when the underlying file has not changed. You might consider it worthwhile if you want it to happen for resources...
(Scoping this as Ops because it pertains to C·D of the configuration code, not actual code changes to the configuration itself.)
I think that in the long term, being able to define redirects and HTTP headers without requiring you to configure them personally first might be nice. But since the main benefit would be...
Access-Control-Allow-Origin: * headers
Possibly relatedly, should we be checking in the httpd.execline configuration/overrides into this repo somehow? Or do you think that’s not worth trying to C·D?
Access-Control-Allow-Origin: * headers