私は日本のAPIチームの技術ライターです。https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Retry-After の原文を読み、日本語の短い運用メモを作ってください。Retry-After が受け付ける二つの形式を示し、delay-seconds の値の単位と、待ち時間をいつから数えるのかを説明してください。原文の根拠を引用してください。クライアントの挙動を実測したとは言わないでください。本文は三つの短い箇条書きにしてください。
10/8/2026, 9:41:19 AM · llm:deepseek:deepseek-v4-flash
> ⚠ Low confidence — Each summary sentence is tied to a verbatim excerpt and model-checked; completeness and independent factual correctness remain unverified. Evidence assessment: 2 evidence-verified sources cover every sub-claim, but corroboration or support strength is limited. Treat this as provisional.
Model-written summary with sentence-level citations. Each sentence is followed by the verbatim source text it was checked against; sentences without a qualifying excerpt were removed.
Research target 1
Requested topic (unverified): “MDN の Retry-After ヘッダーリファレンス原文によれば、Retry-After が受け付ける二つの形式は何か。”
Retry-After は再試行する日付を受け付ける。 Source text: “A date after which to retry.”
Retry-After はレスポンス受信後に遅延する秒数を示す負でない 10 進数の整数も受け付ける。 Source text: “A non-negative decimal integer indicating the seconds to delay after the response is received.”
Further excerpts:
- “再試行する日付。” - “レスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。”
Research target 2
Requested topic (unverified): “MDN の Retry-After ヘッダーリファレンス原文によれば、delay-seconds 形式の値の単位は何か。”
delay-seconds の値は秒単位で、レスポンス受信後に遅延する秒数を示す。 Source text: “A non-negative decimal integer indicating the seconds to delay after the response is received.”
Further excerpts:
- “レスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。”
Research target 3
Requested topic (unverified): “MDN の Retry-After ヘッダーリファレンス原文によれば、待ち時間はいつから数えるのか。”
待ち時間はレスポンスを受信した時点から数える。 Source text: “A non-negative decimal integer indicating the seconds to delay after the response is received.”
Further excerpts:
- “レスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。”
Summary sentences are model-written and model-checked, not independently verified; they claim no more than their excerpts and are not a complete synthesis. Excerpts establish source grounding, not that a source is correct. Source statements may be wrong or conflicting. Payment states remain in the separate receipt.
Supplied original source status
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Retry-After: Bounded text extracted from https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Retry-After; qualifying excerpts retained.
Evidence ledger — recorded source excerpts
Research targets are unverified topics. Coverage is an estimate of excerpt support, not proof of entailment, factual truth or a complete answer.
Requested topic (unverified): “MDN の Retry-After ヘッダーリファレンス原文によれば、Retry-After が受け付ける二つの形式は何か。”
50% estimated“A date after which to retry.” [S1] Retry-After header - HTTP | MDN
“A non-negative decimal integer indicating the seconds to delay after the response is received.” [S1] Retry-After header - HTTP | MDN
“再試行する日付。” [S2] Retry-After ヘッダー - HTTP | MDN
“レスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。” [S2] Retry-After ヘッダー - HTTP | MDN
Requested topic (unverified): “MDN の Retry-After ヘッダーリファレンス原文によれば、delay-seconds 形式の値の単位は何か。”
90% estimated“A non-negative decimal integer indicating the seconds to delay after the response is received.” [S1] Retry-After header - HTTP | MDN
“レスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。” [S2] Retry-After ヘッダー - HTTP | MDN
Requested topic (unverified): “MDN の Retry-After ヘッダーリファレンス原文によれば、待ち時間はいつから数えるのか。”
90% estimated“A non-negative decimal integer indicating the seconds to delay after the response is received.” [S1] Retry-After header - HTTP | MDN
“レスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。” [S2] Retry-After ヘッダー - HTTP | MDN
What if a source were missing?
Temporarily leave out one source to see which research targets retain excerpts in this report.
Showing the original excerpt ledger.
MDN の Retry-After ヘッダーリファレンス原文によれば、Retry-After が受け付ける二つの形式は何か。
4 recorded excerpts remain.
Inspect remaining excerpts
“A date after which to retry.”
S1 · mozilla.org · Retry-After header - HTTP | MDN · version 7a354ac0c63aab9630ce1c054e56ae0d9fa2c006429e8303b5db258a93348675
“A non-negative decimal integer indicating the seconds to delay after the response is received.”
S1 · mozilla.org · Retry-After header - HTTP | MDN · version 7a354ac0c63aab9630ce1c054e56ae0d9fa2c006429e8303b5db258a93348675
“再試行する日付。”
S2 · mozilla.org · Retry-After ヘッダー - HTTP | MDN · version 070dfca82e2fbe9dbb170f145139031b14a56a34a7bad28e2dd6812345f26037
“レスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。”
S2 · mozilla.org · Retry-After ヘッダー - HTTP | MDN · version 070dfca82e2fbe9dbb170f145139031b14a56a34a7bad28e2dd6812345f26037
MDN の Retry-After ヘッダーリファレンス原文によれば、delay-seconds 形式の値の単位は何か。
2 recorded excerpts remain.
Inspect remaining excerpts
“A non-negative decimal integer indicating the seconds to delay after the response is received.”
S1 · mozilla.org · Retry-After header - HTTP | MDN · version 7a354ac0c63aab9630ce1c054e56ae0d9fa2c006429e8303b5db258a93348675
“レスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。”
S2 · mozilla.org · Retry-After ヘッダー - HTTP | MDN · version 070dfca82e2fbe9dbb170f145139031b14a56a34a7bad28e2dd6812345f26037
MDN の Retry-After ヘッダーリファレンス原文によれば、待ち時間はいつから数えるのか。
2 recorded excerpts remain.
Inspect remaining excerpts
“A non-negative decimal integer indicating the seconds to delay after the response is received.”
S1 · mozilla.org · Retry-After header - HTTP | MDN · version 7a354ac0c63aab9630ce1c054e56ae0d9fa2c006429e8303b5db258a93348675
“レスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。”
S2 · mozilla.org · Retry-After ヘッダー - HTTP | MDN · version 070dfca82e2fbe9dbb170f145139031b14a56a34a7bad28e2dd6812345f26037
Targets are requested topics, not verified assertions. Excerpts do not prove truth or independent corroboration. This view keeps the answer, confidence and payments unchanged and makes no new requests.
Research evidence matrix
Compare unverified research targets with cited sources and inspect recorded excerpts. An empty cell means no inspectable excerpt was recorded; it does not establish whether a claim is true, false, or disputed. Coverage and agent confidence do not prove entailment, measured accuracy or complete synthesis.
| Research target (unverified) | Inspection status | [S1] Retry-After header - HTTP | MDNPublication: mozilla.orgPublished: Not recorded | [S2] Retry-After ヘッダー - HTTP | MDNPublication: mozilla.orgPublished: Not recorded |
|---|---|---|---|
| MDN の Retry-After ヘッダーリファレンス原文によれば、Retry-After が受け付ける二つの形式は何か。 | Recorded excerpt | Inspect 2 excerptsA date after which to retry. A non-negative decimal integer indicating the seconds to delay after the response is received. | Inspect 2 excerpts再試行する日付。 レスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。 |
| MDN の Retry-After ヘッダーリファレンス原文によれば、delay-seconds 形式の値の単位は何か。 | Recorded excerpt | Inspect 1 excerptA non-negative decimal integer indicating the seconds to delay after the response is received. | Inspect 1 excerptレスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。 |
| MDN の Retry-After ヘッダーリファレンス原文によれば、待ち時間はいつから数えるのか。 | Recorded excerpt | Inspect 1 excerptA non-negative decimal integer indicating the seconds to delay after the response is received. | Inspect 1 excerptレスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。 |
Reference export
2 article references. Recorded titles, links and dates; observed scholarly records also include supplied authors, DOI and journal metadata with read limits. Review metadata before using in a paper. Import RIS into Zotero with File → Import.
Cited sources and references
- 1Retry-After header - HTTP | MDNmozilla.orgFree public reference · no creator payment · extracted html text60%
- 2Retry-After ヘッダー - HTTP | MDNmozilla.orgFree public reference · no creator payment · extracted html text40%
Decision log · 75 steps
Breaking down: "私は日本のAPIチームの技術ライターです。https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Retry-After の原文を読み、日本語の短い運用メモを作ってください。Retry-After が受け付ける二つの形式を示し、delay-seconds の値の単位と、待ち時間をいつから数えるのかを説明してください。原文の根拠を引用してください。クライアントの挙動を実測したとは言わないでください。本文は三つの短い箇条書きにしてください。"
Identified 3 research target(s) to investigate; these are not established facts
Quick mode: at most 2 paid/cached/public reads, with no marketplace probe or gap-expansion round.
Supplied source URL https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Retry-After admitted as an unread discovery lead. No official authorship or evidence established; a supplied fragment requests a section but only a bounded whole-document read is supported.
Web search: 2/2 planned queries attempted, 1 succeeded, 9 public page previews/leads, 1 unavailable queries. Previews and supplied URLs are discovery only. Public reads spend no USDC; model and service operating costs remain separate.
Discovered 2 verified creator source(s) and 39 free public reference(s)
Recalled 24 past runs on this subject — how these sources performed when they were available.
ERC-8004 reputation loaded — composite scores on this subject.
Claim-aware portfolio (exhaustive; bounded selection, not a claim of global optimality) selected 2/3 positive proposal(s): 2 free/cache selections + 0 paid fresh selections, predicting 3/3 claim(s) above the evidence floor with $0.000000/$0.000000 fetch USDC reserved.
Free-preview pre-check maps an actionable source to every sub-claim (3/3); paid reading may proceed within the budget.
This is the exact caller-requested MDN original URL; reading it is the direct way to verify the two accepted formats, the delay-seconds unit, and when the wait starts, for all three targets. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — selected for the claim-aware evidence portfolio (targets claims 1, 2, 3; 0 fetch USDC, 1 attention slot).
Japanese MDN translation of the same Retry-After reference; its preview shows the directive definitions including the non-negative integer seconds and the date form, useful for targets 0-2 and for Japanese phrasing. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — selected for the claim-aware evidence portfolio (targets claims 1, 2, 3; 0 fetch USDC, 1 attention slot).
arXiv rate-limit policy post concerns preprint platform moderation, not the MDN Retry-After header reference; no target is worth investigating here. - free public feed reference; no purchase or creator reward.
BIS working paper on gold prices and geopolitics is unrelated to HTTP Retry-After semantics. - free public feed reference; no purchase or creator reward.
AI agents essay does not cover the MDN Retry-After header reference or its syntax. - free public feed reference; no purchase or creator reward.
Cloudflare Workers module registry post is about Node.js compatibility, not Retry-After header documentation. - free public feed reference; no purchase or creator reward.
Open heritage roundtable post is unrelated to HTTP header semantics. - free public feed reference; no purchase or creator reward.
Private AI compute announcement has no bearing on Retry-After formats or delay-seconds units. - free public feed reference; no purchase or creator reward.
OA Journals Toolkit article is unrelated to the MDN Retry-After reference. - free public feed reference; no purchase or creator reward.
Docker ecosystem event post does not document HTTP Retry-After. - free public feed reference; no purchase or creator reward.
DuckDB view-only database article is unrelated to HTTP header semantics. - free public feed reference; no purchase or creator reward.
AI working practices essay does not address Retry-After formats or timing. - free public feed reference; no purchase or creator reward.
Go 1.27 release notes are unrelated to the MDN Retry-After header reference. - free public feed reference; no purchase or creator reward.
Federated learning privacy research has no relevance to HTTP Retry-After documentation. - free public feed reference; no purchase or creator reward.
LLM agent post does not cover Retry-After header syntax or delay-seconds units. - free public feed reference; no purchase or creator reward.
Microsoft Research Asia lab recap is unrelated to the requested HTTP header reference. - free public feed reference; no purchase or creator reward.
WebMCP challenge announcement does not document Retry-After semantics. - free public feed reference; no purchase or creator reward.
Ollama decision-model announcement is unrelated to HTTP Retry-After. - free public feed reference; no purchase or creator reward.
OpenAI Docs MCP quickstart concerns MCP server setup, not the MDN Retry-After header reference. - free public feed reference; no purchase or creator reward.
OpenAlex software citation post is unrelated to HTTP header documentation. - free public feed reference; no purchase or creator reward.
PostgreSQL BM25 extension news does not cover Retry-After formats or timing. - free public feed reference; no purchase or creator reward.
PyTorch conference track announcement is unrelated to the requested header reference. - free public feed reference; no purchase or creator reward.
Rust 1.99.0 release announcement has no bearing on Retry-After semantics. - free public feed reference; no purchase or creator reward.
Post-training LLM article is unrelated to HTTP Retry-After documentation. - free public feed reference; no purchase or creator reward.
Spotify data lake indexing post does not document Retry-After header behavior. - free public feed reference; no purchase or creator reward.
Stripe stablecoin announcement is unrelated to the MDN Retry-After reference. - free public feed reference; no purchase or creator reward.
Supabase Select recap does not cover Retry-After formats, units or timing. - free public feed reference; no purchase or creator reward.
Tailscale blog about Codex Cloud networking; unrelated to the Retry-After header reference and its two formats, units, or timing. - free public feed reference; no purchase or creator reward.
NASA engineering excellence essay; no connection to HTTP Retry-After semantics. - free public feed reference; no purchase or creator reward.
vLLM disaggregated serving guide; unrelated to the Retry-After header targets. - free public feed reference; no purchase or creator reward.
Wikimedia community workshop story; not about HTTP headers or Retry-After. - free public feed reference; no purchase or creator reward.
x402 payments foundation announcement; HTTP payments topic, not the Retry-After header reference. - free public feed reference; no purchase or creator reward.
http.dev guide previews the two Retry-After formats (delta-seconds vs HTTP-date) and the seconds unit; a plausible secondary read for targets 0 and 1, though not the requested MDN original. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 2-source attention and $0.000000 fetch-budget caps, so this proposal stays unspent.
Sportmonks glossary page covers the two formats but is a vendor glossary; the requested MDN original and http.dev guide are more direct, so this is redundant for targets 0-1. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Japanese blog note on Retry-After; derivative of the same spec and less authoritative than the MDN originals for targets 0-2. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Chinese MDN translation of the same page; the English requested original and Japanese MDN version already cover targets 0-2, making this redundant. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Medium article is paywalled and derivative; not a first-hand reference for the MDN wording needed for targets 0-2. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Blog quoting RFC 9110 on Retry-After; relevant background but the requested MDN original is the authoritative source for targets 0-2. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Japanese vendor tech-blog explainer on Retry-After; derivative and less direct than the MDN originals for targets 0-2. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Keryx release notes about npm ci retries and research synthesis; unrelated to HTTP Retry-After header semantics, and paid at $0.005.
Keryx buyer-recovery engineering doc about quoting and resuming paid jobs; no bearing on Retry-After formats, units, or timing, and paid at $0.002.
READ https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Retry-After - selected original public page, 0 USDC; not a cache hit.
Read extracted public text from https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Retry-After - S1; quote matching establishes source grounding, not fact verification.
READ Retry-After ヘッダー - HTTP | MDN - selected original public page, 0 USDC; not a cache hit.
Read extracted public text from https://developer.mozilla.org/ja/docs/Web/HTTP/Reference/Headers/Retry-After - S2; quote matching establishes source grounding, not fact verification.
Final check — "MDN の Retry-After ヘッダーリファレンス原文によれば、Retry-After が受け付ける二つの形式は何…": 100% assessed by S1, S2
Final check — "MDN の Retry-After ヘッダーリファレンス原文によれば、delay-seconds 形式の値の単位は何か。": 100% assessed by S1, S2
Final check — "MDN の Retry-After ヘッダーリファレンス原文によれば、待ち時間はいつから数えるのか。": 100% assessed by S1, S2
Final coverage assessment — MDN の英語原文（S1）と日本語版（S2）の両方に、Retry-After の構文・ディレクティブの説明が含まれており、三つのサブクレームすべてに直接答えている。S1 の Syntax 節に二形式（<http-date> と <delay-seconds>）が示され、Directives 節で <delay-seconds> は「seconds to delay after the response is received」と説明されている。S2 も同内容を日本語で示しており、待ち時間の起点は「レスポンスを受信してから」と明記されている。クライアント挙動の実測に関する記述は求められておらず、原文引用の根拠として十分。
Synthesizing a grounded answer from 2 source(s)…
Relevance review returned; only checked excerpts can retain support, and review cannot raise it.
Delivering 4 summary sentence(s), each tied to one checked verbatim excerpt; complete synthesis remains unverified.
Source-matched public excerpt (no creator reward) — S1, research target 1, proposed support 50% (estimate, not entailment): “A date after which to retry.”
Source-matched public excerpt (no creator reward) — S1, research target 1, proposed support 50% (estimate, not entailment): “A non-negative decimal integer indicating the seconds to delay after the response is received.”
Source-matched public excerpt (no creator reward) — S1, research target 2, proposed support 90% (estimate, not entailment): “A non-negative decimal integer indicating the seconds to delay after the response is received.”
Source-matched public excerpt (no creator reward) — S1, research target 3, proposed support 90% (estimate, not entailment): “A non-negative decimal integer indicating the seconds to delay after the response is received.”
Source-matched public excerpt (no creator reward) — S2, research target 1, proposed support 50% (estimate, not entailment): “再試行する日付。”
Source-matched public excerpt (no creator reward) — S2, research target 1, proposed support 50% (estimate, not entailment): “レスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。”
Source-matched public excerpt (no creator reward) — S2, research target 2, proposed support 90% (estimate, not entailment): “レスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。”
Source-matched public excerpt (no creator reward) — S2, research target 3, proposed support 90% (estimate, not entailment): “レスポンスを受信してから遅延する秒数を示す負でない 10 進数の整数。”
Prepared a sentence-cited summary from 2 source(s)
Confidence: Low — Each summary sentence is tied to a verbatim excerpt and model-checked; completeness and independent factual correctness remain unverified. Evidence assessment: 2 evidence-verified sources cover every sub-claim, but corroboration or support strength is limited.
mozilla.org contributed 60% - free public reference; reward share withheld
mozilla.org contributed 40% - free public reference; reward share withheld
Done. Spent $0 across 0 confirmed/simulated payment(s) to creators.
Portable research receipt
Take the evidence trail with you
One deterministic JSON bundle binds the answer, visible decisions, exact article versions, claim evidence and a Circle-settlement snapshot under SHA-256. Retain the digest to detect later changes; the self-check is not a publisher or Keryx signature.
Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.