4 ms·
"HTML on disk" does not cover headers. But it's true that cloud providers have that solved, and "DIY" bring-your-own-server don't, and the article somehow conc
by the_gipsy 4y ago
"HTML on disk" does not cover headers.
But it's true that cloud providers have that solved, and "DIY" bring-your-own-server don't, and the article somehow concludes that bringing your own server with the right configuration is not an option.
- ciprian_craciun 4y ago> [...] the article somehow concludes that bringing your own server with the right configuration is not an option. [the author here] On the contrary, it is an option to fine-tune your web-server configuration to put all the right headers in the right places. (I usually do this from HAProxy and just ignore the web-server.) However, the point I was trying to make in the article is that where these headers are configured is divorced from the content itself lives. I can't look at a HTML file and easily say "when the browser will hit this resource these are the HTTP headers that will be sent in the reply"; I need to execute in my mind the web server configuration logic to get that. Thus my proposal is to move back (some of) the headers where they belong: as meta-data right besides the actual resource.
- the_gipsy 4y agoBut do you really need different headers for different resources for a static site? I can imagine a distinct "downloads" folder maybe, but not much more.