Skip to content

gateway: clean Cache-Control and Last-Modified #436

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

Merged
lidel merged 2 commits into from
Sep 25, 2023
Merged

gateway: clean Cache-Control and Last-Modified #436

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
56de6ec
gateway: clean Cache-Control and Last-Modified
hacdias Sep 5, 2023
1148af2
chore: apply feedback suggestions
hacdias Sep 7, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions src/http-gateways/path-gateway.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -370,17 +370,18 @@ in caches.

Returned directive depends on requested content path and format:

- `Cache-Control: public, max-age=29030400, immutable` must be returned for
- `Cache-Control: public, max-age=29030400, immutable` MUST be returned for
every immutable resource under `/ipfs/` namespace.

- `Cache-Control: public, max-age=<ttl>` should be returned for mutable
resources under `/ipns/{id-with-ttl}/` namespace; `max-age=<ttl>` should
indicate remaining TTL of the mutable pointer such as IPNS record or DNSLink
- `Cache-Control: public, max-age=<ttl>` SHOULD be returned for mutable
resources under `/ipns/{id-with-ttl}/` namespace; `max-age=<ttl>` SHOULD
indicate remaining TTL of the mutable pointer such as :cite[ipns-record] or DNSLink
TXT record.
- Implementations MAY place an upper bound on any TTL received, as
noted in Section 8 of :cite[rfc2181].
- If TTL value is unknown, implementations SHOULD set it to a static
value, but it SHOULD not be lower than 60 seconds.
- If TTL value is unknown, implementations SHOULD not send a `Cache-Control`
- No matter if TTL value is known or not, implementations SHOULD always
send a [`Last-Modified`](#last-modified-response-header) header with the timestamp of the record resolution.

### `Last-Modified` (response header)

Expand Down