Skip to content

Cache or eTag resources in /assets folder #1092

Open

Description

@Marc-Andre-Rivet

We currently eTag / cache resources included in the component repos but do not offer any cache mechanism for resources in /assets. The same mechanism could be applied:

  • known assets included in the index_template are fingerprinted using the same versioning / last_modified logic with version=0.0.0
  • assets that are not requested through the index_template revert to using eTag

Activity

  1. added this to the Dash v1.x milestone on Jan 20, 2020
  2. chriddyp commented on Jan 31, 2020

    @chriddyp
    Member

    @Marc-Andre-Rivet - when I load dash.plot.ly and look at the network console, it looks like assets are cached and have a 304 response. What am I missing?

    image

  3. chriddyp commented on Jan 31, 2020

    @chriddyp
    Member

    Additionally, the component package JS files look like they aren't getting cached (all of those 200s)

  4. self-assigned this
    on Jul 17, 2024
  5. removed their assignment
    on Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3backlogfeaturesomething new

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions