HTTP last-modified header for Pages files is set to when whole respository was updated, not individual file #1805

Comment

The HTTP "last-modified" header for html pages hosted on Codeberg Pages seems to be set to the time and date of the most recent update to the whole repository, rather than the most recent update to that specific html file.

Is this intentional, or a known issue?

I use Javascript to show the timestamp when pages were last changed, so this is resulting in all of the pages in my pages repository showing the date of the last update to the repository, which isn't necessarily the date when the pages were changed.

It's probably a pretty low-priority issue, but it'd be good to know if it's something that will be fixed in the future 🙏

@ashraya wrote in #1805 (comment):

Is this intentional, or a known issue?

It seems intentional, the most recent update to the branch is taken as value for Last-Modified. CC @crapStone maybe something to consider for the newest pages server?

@Gusted wrote in #1805 (comment):

It seems intentional, the most recent update to the branch is taken as value for Last-Modified.

Thank you for replying and for the information.

It'd be interesting to know the reasoning behind the choice if it is intended. It seems a little consistent with how the header is used elsewhere, and might result in more traffic/load for Codeberg than is necessary (as files will appear from headers to have been updated even when nothing about them has changed).