@@ -266,8 +266,7 @@ making a new request.
266
266
267
267
Error to indicate that request was formally correct, but this specific Gateway
268
268
is unable to return requested data due to legal reasons. Response SHOULD
269
- include an explanation, as noted in
270
- [ RFC7725.html#n-451-unavailable-for-legal-reasons] ( https://httpwg.org/specs/rfc7725.html#n-451-unavailable-for-legal-reasons ) .
269
+ include an explanation, as noted in Section 3 of : cite [ rfc7725] .
271
270
272
271
See: [ Denylists] ( #denylists )
273
272
@@ -286,7 +285,7 @@ Returned when Gateway was not able to produce response under set limits.
286
285
Used for HTTP caching.
287
286
288
287
An opaque identifier for a specific version of the returned payload. The unique
289
- value must be wrapped by double quotes as noted in [ RFC7232#Etag ] ( https://httpwg.org/specs/rfc7232.html#header.etag ) .
288
+ value must be wrapped by double quotes as noted in Section 8.8.3 of : cite [ rfc9110 ] .
290
289
291
290
In many cases it is not enough to base ` Etag ` value on requested CID.
292
291
@@ -334,7 +333,7 @@ Returned directive depends on requested content path and format:
334
333
indicate remaining TTL of the mutable pointer such as IPNS record or DNSLink
335
334
TXT record.
336
335
- Implementations are free to place an upper bound on any TTL received, as
337
- noted in [ RFC 2131 Section 8] ( https://datatracker.ietf.org/doc/html/rfc2181#section-8 ) .
336
+ noted in Section 8 of : cite [ rfc2131 ] .
338
337
- If TTL value is unknown, implementations are free to set it to a static
339
338
value, but it should not be lower than 60 seconds.
340
339
@@ -354,7 +353,7 @@ Returning this header depends on the information available:
354
353
- Legacy implementations set this header to the current timestamp when reading
355
354
TTL on ` /ipns/ ` content paths was not available. This hint was used by web
356
355
browsers in a process called "Calculating Heuristic Freshness"
357
- ([ RFC7234 ] ( https://tools.ietf.org/html/rfc7234#section- 4.2.2) ). Each browser
356
+ (Section 4.2.2 of : cite [ rfc9111 ] ). Each browser
358
357
uses different heuristic, making this an inferior, non-deterministic caching
359
358
strategy.
360
359
@@ -408,7 +407,7 @@ To illustrate, `?filename=testтест.pdf` should produce:
408
407
` Content-Disposition inline; filename="test____.jpg"; filename*=UTF-8''test%D1%82%D0%B5%D1%81%D1%82.jpg `
409
408
410
409
- ASCII representation must have non-ASCII characters replaced with ` _ `
411
- - UTF-8 representation must be wrapped in Percent Encoding ([ RFC 3986, Section 2.1] ( https://www.rfc-editor.org/rfc/ rfc3986.html#section-2.1 ) ).
410
+ - UTF-8 representation must be wrapped in Percent Encoding (Section 2.1 of : cite [ rfc3986] ).
412
411
- NOTE: ` UTF-8'' ` is not a typo – see [ Examples in RFC5987] ( https://datatracker.ietf.org/doc/html/rfc5987#section-3.2.2 )
413
412
414
413
` Content-Disposition ` must be also set when a binary response format was requested:
0 commit comments