[Bug] webfetch hangs on HTTP/2 stream errors and blocked responses

Resolved 💬 3 comments Opened Oct 21, 2025 by zac-almeida Closed Jan 8, 2026

Bug Description
When fetching a URL that implements a type of blocking or has HTTP stream errors, webfetch gets stuck waiting for a response.

This is the type of response that makes webfetch stuck:
curl https://travel.usnews.com/Grand_Canyon_AZ/When_To_Visit/
curl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)

Environment Info

  • Platform: linux
  • Terminal: vscode
  • Version: 2.0.25
  • Feedback ID: 0c428e3c-2943-477f-91b3-6d8690d0b265

Errors

[]

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗