🐛 BUG: Wrangler local dev server unbale to handle HTTP/2 requests (Wrong ALPN)

[MrAshFar]

Which Cloudflare product(s) does this pertain to?

Workers Runtime

What version(s) of the tool(s) are you using?

3.6.0

What version of Node are you using?

18.16.1

What operating system are you using?

win64

Describe the Bug

I started the wrangler local dev server by using the below command:

$ wrangler dev --local-protocol https --port 443 --log-level debug

Then When I send an HTTP/2 request to the server, it throws:

workerd/server/server.c++:2528: error: Uncaught exception: kj/async-io-win32.c++:385: failed: WSARecv(): #64 The specified network name is no longer available.

The client-side complains:

ALPN Protocol Error

Please provide a link to a minimal reproduction

No response

Please provide any relevant error logs

workerd/server/server.c++:2528: error: Uncaught exception: kj/async-io-win32.c++:385: failed: WSARecv(): #64 The specified network name is no longer available.

[mrbbot]

Hey! 👋 Thanks for raising this, and apologies for the delayed response. I don't think we'll implement this feature. This would require us to add a HTTP/2 proxy to Wrangler, or add native HTTP/2 support to the Workers runtime, which I don't think we'll be able to do. I'd recommend putting a reverse proxy such as NGINX in front of wrangler dev's server. See #2118 (comment) for a starting configuration.