Taking Apache as an example, the code output may look like this:

# for all responses
<IfModule mod_headers.c>
  Header set "Cache-Control" 'no-cache'
</IfModule>

# for single response
Header set "Cache-Control" 'no-cache'

Actually both these cases set the header for all responses.

If you want a header only to be included in a response for certain files based on file extension you could use e.g. <FilesMatch>, or preferably based on MIME type using expr.

<IfModule mod_headers.c>

  # Based on file extension:
  <FilesMatch "\.(htm|html)$">
    Header set Cache-Control "no-cache"
  </FilesMatch>

  # Based on MIME-Type:
    Header set Cache-Control "no-cache" "expr=%{CONTENT_TYPE} =~ m#text/html#i

</IfModule>

Perhaps there could be an option to choose which MIME-types or file extensions the build should apply to?

Whey you use max-age, code that is generated in express shows following:

res.set('Cache-Control', 'max-age 86400');

shouldn't there be = instead of space, like so

res.set('Cache-Control', 'max-age=86400');

Thank you

First of all, great tool! Nice job on this.

In Firefox, the "share | copy" links in the header are being overlaid by the element in the HTML called <div class="resultHeader">. So in Firefox, you can't actually use those links because they're overlaid by the element due to the margin-top: -40px in the CSS.

I'm not entirely sure why the same problem doesn't occur in Chrome, because it also seems to be overlaid in that browser, but the links still seem to work there.

only-if-cached is a request directive, so it seems it'd be incorrect to include it in a response, see https://tools.ietf.org/html/rfc7234#section-5.2.1.7