GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Server should include the Last-Modified header · Issue #1793 · nodeSolidServer/node-solid-server

Server should include the Last-Modified header  #1793

New issue
Copy link
New issue
Copy link
Open
#1875
#1856
Open
Server should include the Last-Modified header #1793
#1875
#1856
Copy link
Assignees
knishkagithub
Labels
featuregood first issueAn issue that should be quite easy for newcomers to fixAn issue that should be quite easy for newcomers to fix

Description

@csarven
csarven
opened on Sep 10, 2024
Issue body actions

Server MUST generate a Last-Modified header field in response to GET and HEAD requests.

https://solidproject.org/ED/protocol#server-last-modified-includes

Servers are strongly discouraged from exposing information beyond the minimum amount necessary to enable a feature.

https://solidproject.org/ED/protocol#exposing-information

So, the implementation should only expose the Last-Modified header when access is granted to the request target, i.e., when user or public has Read access to the resource. This is typically aligned with the 200 response.

Activity

  1. csarven
    added
    feature
    good first issueAn issue that should be quite easy for newcomers to fixAn issue that should be quite easy for newcomers to fix
    on Sep 10, 2024

  2. csarven commented on Sep 10, 2024

    @csarven
    csarven
    on Sep 10, 2024
    MemberAuthor
    More actions

    The modified timestamp can be easily retrieved using fs.stat and mtime.

    Here is a screencast showing an application making use of the header field in one particular way:

    https://dokie.li/media/video/dokieli-last-modified.webm

    dokieli-last-modified.webm

    See also solid/specification#678 (comment)

  3. knishkagithub commented on Oct 7, 2024

    @knishkagithub
    knishkagithub
    on Oct 7, 2024
    More actions

    i would like to work in this issue,could you please assign it to me

  4. bourgeoa
    assigned
    knishkagithub
    on Oct 7, 2024

  5. csarven commented on Oct 12, 2024

    @csarven
    csarven
    on Oct 12, 2024
    MemberAuthor
    More actions

    @knishkagithub , not sure if you got a notification about @bourgeoa assigning this issue to you but all yours now. Thanks!

  6. melvincarvalho commented on Apr 8, 2025

    @melvincarvalho
    melvincarvalho
    on Apr 8, 2025
    Contributor
    More actions

    @knishkagithub just wondering how you're getting on with this, as it's been 6 months. Need any help?

  7. AlyNotMe commented on Sep 23, 2026

    @AlyNotMe
    AlyNotMe
    on Sep 23, 2026
    More actions

    Hi, since there's been no activity for 6 months, would it be okay if I take this over? Happy to wait a bit for a reply, but wanted to check in case the original assignee has moved on. Thanks!

  8. AlyNotMe
    added a commit that references this issue on Sep 23, 2026

    fix: add Last-Modified header to GET and HEAD responses

    This issue will close once commit 60402ad is merged into the 'main' branch.
    60402ad

  9. bourgeoa commented on Sep 23, 2026

    @bourgeoa
    bourgeoa
    on Sep 23, 2026
    Member
    More actions

    Thanks. I shall review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @knishkagithub
    knishkagithub

Labels

featuregood first issueAn issue that should be quite easy for newcomers to fixAn issue that should be quite easy for newcomers to fix

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.