Unverified50% confidenceOpinionExact time
Replay XHR cannot correctly reproduce Fetch requests, which is the fundamental reason it was replaced by Resend.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/12/2026
First Seen
Valid until: 1/10/2027
Sources
Related Entities
Related Claims
UnverifiedThe Replay XHR feature existed for nearly a decade and was mainly used to resend captured XHR requests.79% similarUnverifiedIn replay tests, the same requestId is submitted twice consecutively; the first time the replay flag is false, the second time it should be identified as a duplicate request with replay as true, both returning the same order number with only one business change produced.60% similarUnverifiedIn the cache reuse mechanism, once the request prefix is modified, the cache for all content after it becomes invalid; modifying tools or other parts of the request will still affect reuse.59% similarUnverifiedThe fix involves reusing already-persisted tool rejection results during the approval resumption process (commit hash d9e04cb).56% similarUnverifiedIf the refresh token is placed in localStorage, an XSS occurrence is equivalent to account compromise.56% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1010996API
curl https://kongchang.com/api/v1/knowledge/claims/1010996MCP
get_claim(id=1010996)