Skip to content

Asset fingerprinting and SRI #519

@RealOrangeOne

Description

@RealOrangeOne

It'd be nice if there were a way of accessing a fingerprint or hash of static files, for a more reliable way of caching assets.

I've given this a bit of thought, and probably need some input.

Ideally, it'd just be an additional function, say get_static, which returned a structure which contained the path, fingerprinted URL, hash, things like that. Because this requires the static files to exist before running, it would also serve as a link checker. However, What do we do about live reloading? When editing a static file, we'd either need to keep track of the linked resources per page, and only reload the linked pages, or just reload the whole site. (The latter is so much easier!)

I see no reason why this couldnt work for any static file in the site, eg images. It wouldnt play well with images after they've been processed, but static images should work fine!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions