Skip to content

Cache Busting #108

@avivace

Description

@avivace

After having applied an update, the browser sometimes loads a cached version of the vue-app resources. The vue-app build needs to expire after a successful updates or one of this situation can happen:

  • blank index.html, because the webpack artifacts changed names
  • cached js artifacts. if the build introduced breaking or semi-breaking API changes, old routes will be called (with 500/404 responses) making some features unusable until a force refresh (CTRL+F5) happens. Things can also break if the API works but it's not supposed to handle data in a deprecated format.

I'm opening this here but it's possible we can fix this in vue-app.

some examples of cache busting
http://flask.pocoo.org/snippets/40/

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