-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dashboard should configure response compression & caching for static assets #4150
Comments
Just curious is this only noticeable in the case where the dashboard is on a different machine? |
From a UX perspective, most likely. |
TBC the dashboard is configuring the |
* Add response compression for static assets to the dashboard Fixes #4150 * Use allow list for compressed MIME types
The dashboard currently doesn't configure compression or caching headers for the static assets it delivers, including libraries like plotly (which is 3.5 MB).
We should configure the response compression middleware to ensure that at least static assets are compressed (and potentially the HTML output too), and investigate setting cache headers for static assets with versioned paths to help improve the client-side experience.
The text was updated successfully, but these errors were encountered: