mirror of
https://github.com/denoland/deno.git
synced 2025-10-01 22:51:14 +00:00
48ccb67131
Deno.serve `Request` abort signals are aborted by default even when it is finished successfully. This PR gates this behavior behind the "legacy_abort" which is the default right now. Turning the `no_legacy_abort` runtime option on is a **breaking change** and will only abort request signals when there is a failure, thereby cannot be used to determine if the request finished. This aligns with `fetch` API. Ref https://github.com/denoland/deno/issues/27005 |
||
|---|---|---|
| .. | ||
| benches | ||
| 00_serve.ts | ||
| 01_http.js | ||
| 02_websocket.ts | ||
| Cargo.toml | ||
| compressible.rs | ||
| fly_accept_encoding.rs | ||
| http_next.rs | ||
| lib.rs | ||
| network_buffered_stream.rs | ||
| reader_stream.rs | ||
| README.md | ||
| request_body.rs | ||
| request_properties.rs | ||
| response_body.rs | ||
| service.rs | ||
| websocket_upgrade.rs | ||