Does Inertia.js provide a mechanism to signal request cancellation to the server?

Answer

No, Inertia.js does not provide a built‑in header or hook that automatically tells the server a request has been aborted. The client uses AbortController to cancel the network call, but the abort is limited to the browser’s TCP socket; the HTTP request itself is never marked as cancelled by Inertia.

Why the Server Doesn’t See the Abort

When a new visit starts, Inertia calls controller.abort() on the previous fetch request. The browser sends a FIN packet to the server, but the HTTP request is still considered “completed” from the server’s point of view unless the server explicitly checks for an aborted socket.

Confirmed Server‑Side Detection Techniques

Most server runtimes expose an event or function that fires when the underlying socket is closed before the response is sent:

• Node/Express: req.on('aborted', () => {/* handle abort */})
• Koa: ctx.req.on('aborted', () => {/* handle abort */})
• PHP (Laravel, Symfony, etc.): if (connection_aborted()) { abort(499); }
• Python (FastAPI/Starlette): use request.is_disconnected() in async handlers.
• Go (net/http): req.Context().Done() signals cancellation.

These hooks fire as soon as the client closes the TCP connection, allowing you to skip expensive work or roll back partial database changes.

Practical Steps for a Typical Inertia + Server Setup

1. Wrap expensive logic in an abort check. For example, in a Laravel controller:

   if (connection_aborted()) {
       // Client left early – abort further processing
       abort(499);
   }
   // Normal controller code here
   

2. Use the request‑level abort event in Node.

   app.use((req, res, next) => {
       req.on('aborted', () => {
           console.log('Client aborted visit', req.originalUrl);
       });
       next();
   });
   

3. Optional: Send a custom header if you need correlation. Add a header like X-Inertia-Visit-Id: <uuid> on the client (you can generate it in the Inertia visit options) and read it on the server to match abort events with specific visits.
4. Test the flow. Trigger a long‑running Inertia visit, then click another link to cancel it. Verify that the abort handler runs before the expensive database query starts.

When You Might Need a Custom Header

If your backend is behind a reverse proxy that may swallow the TCP FIN (e.g., NGINX with proxy_buffering on;), the abort event may never reach your application. In that case, sending a lightweight header that the proxy forwards can give you a reliable signal. The server can then ignore the request body or abort a database transaction if the header indicates the client has navigated away.

What’s Still Uncertain

Inertia itself does not expose any cancellation hooks, so any integration relies on the underlying server’s abort detection. The exact behavior can vary with proxy configuration, language runtime, and framework version. If you encounter a scenario where aborts aren’t detected, please share the backend stack and proxy setup so we can refine the recommendation.