use same semantic as fastly to deliver static files

[tripodsan]

best would be to consider the manifest.json if to deliver a static file or not.
otherwise, for now just check if file exists below ./dist/

[trieloff]

Quick recap on how our VCL does it:

• fetch the requested path from the action
• if status==404, retry using static delivery

[tripodsan]

I also see:

a) manifest in edge

• list of static files is in edge directly.
• fastly chooses source accordingly

b) manifest in (default) action

• fetch the requested path from the action
• action contains manifest and can very quickly decide if resource is static or not
• if status==404, retry using static delivery

c) action can provide good redirect to resource (big files)

• fetch the requested path from the action
• action contains manifest and can very quickly decide if resource is static or not
• action replies with redirect to static source if required
• fastly fetches resource and merges with cache control headers

d) use /dist/* as prefix

• rewrite all HTML in such a way that references to static files have a /dist prefix
• fastly chooses source accordingly