Capacitor HTTP request cancellation and timeout configuration

Native HTTP Request Lifecycle Management

Ionic applications utilizing the Capacitor HTTP plugin to bypass CORS and improve performance rely on native bridge calls for network operations. While this provides native performance, it introduces a discrepancy in how asynchronous requests are managed compared to the standard browser Fetch API.

A primary challenge arises when implementing strict timeout policies or canceling pending requests during component destruction. Because Capacitor HTTP operates outside the standard browser XHR/Fetch lifecycle, AbortController may not consistently terminate the underlying native network task on iOS or Android.

There is uncertainty regarding the most reliable way to ensure native resources are released when a user navigates away from a page before a large payload is received.

• Does the Capacitor HTTP plugin provide a native mechanism to cancel a specific pending request by ID?
• What is the recommended configuration to synchronize native timeout behaviors across different mobile platforms without relying solely on Promise.race()?