ipfs / ipfs/specs

bug: spec contradiction

Open
#467 0 comments 2 reactions 1 assignee Claimed by @lidel View on GitHub
Dominant language
HTML
Stars
1.2k
Forks
247
Avg merge
5d 21h
Merged PRs (30d)
4

Description

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](https://specs.ipfs.tech/http-gateways/path-gateway/#last-modified-response-header) 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”.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.