Does the Stack Overflow API support client‑initiated request cancellation via HTTP headers?

When building interactive applications that call the Stack Overflow API, developers need a reliable way to abort long‑running requests—for example, when a user navigates away or cancels a search. The API documentation mentions rate‑limit headers and standard HTTP status codes, but it does not specify whether clients can signal cancellation through a dedicated header, query parameter, or by relying on generic timeout mechanisms.

Because the behavior is not documented, it is unclear whether the server respects common abort signals such as the Cancel or X‑Request‑Abort headers, or if it treats a dropped TCP connection as the only cancellation indicator.

What mechanisms, if any, does the Stack Overflow API provide for client‑initiated request cancellation? Which headers or parameters are honored to abort an in‑flight call, and how does this interact with the existing rate‑limit and timeout policies?