{"version":"2.1.274","anchor":"long-running-proxied-requests-now-suppress-fetchs-own-timeo","canonical_anchor":"long-running-proxied-requests-now-suppress-fetchs-own-timeo","heading":"Long-running proxied requests now suppress fetch's own timeout","tier":"notice","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/long-running-proxied-requests-now-suppress-fetchs-own-timeo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Long-running proxied requests now suppress fetch's own timeout\n\nVery long proxied requests can now skip the HTTP client's own timeout when a longer timeout is requested\n\n**What**\n\nTwo internal network request helpers now disable the underlying HTTP client's built-in timeout whenever the caller asks for a timeout longer than 300000 milliseconds (5 minutes). Previously, the client's own timeout could still cut the request short even when a longer timeout was requested.\n\n**Why**\n\nThis lets requests that are meant to run for a long time, such as slow or heavily proxied operations, actually run that long, instead of being cut off by a timeout mechanism the caller never intended to trigger.\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}