Enable client-side icon cache (HTTP Header) #4224

Closed
opened 2026-03-07 19:34:42 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @Crow-Control on GitHub (Jan 30, 2020).

Subject of the issue

Currently Icons are not cached client side, it would be nice if this gets made possible.

Expected behaviour

Icons are not a big risk being cached client side, expected would be that icons are client-cached by default or at least client-side icon caching is enabled using the web headers.

Actual behaviour

No icons are cached because the following header is set on the icons:
cache-control: no-cache, no-store, max-age=0

Originally created by @Crow-Control on GitHub (Jan 30, 2020). ### Subject of the issue Currently Icons are not cached client side, it would be nice if this gets made possible. ### Expected behaviour Icons are not a big risk being cached client side, expected would be that icons are client-cached by default or at least client-side icon caching is enabled using the web headers. ### Actual behaviour No icons are cached because the following header is set on the icons: `cache-control: no-cache, no-store, max-age=0`
Author
Owner

@dani-garcia commented on GitHub (Jan 30, 2020):

Oh this makes perfect sense! Implemented in ebb36235a7 thanks!

@dani-garcia commented on GitHub (Jan 30, 2020): Oh this makes perfect sense! Implemented in https://github.com/dani-garcia/bitwarden_rs/commit/ebb36235a70a2c539a7656454de3478ae776aa22 thanks!
Author
Owner

@Crow-Control commented on GitHub (Jan 30, 2020):

Thats... fast!
Thanks!

@Crow-Control commented on GitHub (Jan 30, 2020): Thats... fast! Thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#4224