github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 03:27:53 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #261] Add cache-control headers to background images #6020

New Issue
Open
opened 2026-04-20 16:33:03 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 16:33:03 -05:00
Owner
Copy Link

Originally created by @RayBB on GitHub (May 7, 2024).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/261

Description

We should add cache control headers to the background images.
That way each time you load the projects page it doesn't have to fully load those images from scratch.

Probably should be added here:
e58d10bc72/pkg/routes/static.go (L248-L252)

This is the url: https://try.vikunja.io/api/v1/projects/4/background

Vikunja Version

Version: v0.23.0

Browser and version

FF 125

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

image
Originally created by @RayBB on GitHub (May 7, 2024). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/261 ### Description We should add cache control headers to the background images. That way each time you load the projects page it doesn't have to fully load those images from scratch. Probably should be added here: https://github.com/go-vikunja/vikunja/blob/e58d10bc72a35c6bc72ff1fc429b246e8faa2c87/pkg/routes/static.go#L248-L252 This is the url: https://try.vikunja.io/api/v1/projects/4/background ### Vikunja Version Version: v0.23.0 ### Browser and version FF 125 ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots <img width="1512" alt="image" src="https://github.com/go-vikunja/vikunja/assets/921217/6be72a53-fea2-4b96-8e28-15b1a045b762">
GiteaMirror added the area/apiarea/themingconcern/performance labels 2026-04-20 16:33:04 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label area/api area/theming concern/performance
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6020
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?