Skip to content
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.

Sign up for GitHub

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

Jump to bottom

bug: spec contradiction #467

Open
SgtPooki opened this issue Mar 15, 2024 · 0 comments · May be fixed by #470
Open

bug: spec contradiction #467

SgtPooki opened this issue Mar 15, 2024 · 0 comments · May be fixed by #470
Assignees
@lidel

Comments

@SgtPooki
Copy link
Member

SgtPooki commented Mar 15, 2024 •
edited
Loading

https://github.com/ipfs/specs/blame/937754aa4b7aa96763be40e1503a4fda3f766ad6/src/http-gateways/path-gateway.md#L401-L402

No matter if TTL value is known or not, implementations should always send a Last-Modified header with the timestamp of the record resolution.

and the link points to https://specs.ipfs.tech/http-gateways/path-gateway/#last-modified-response-header:

New implementations should not return this header if TTL is not known; providing a static expiration window in Cache-Control is easier to reason about than cache expiration based on the fuzzy “heuristic freshness”.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lidel lidel

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

gateway: clarify Last-Modified ipfs/specs
2 participants
@lidel @SgtPooki