TCP connect API and port 443
I am considering using Workers as a scalable proxy for https://webvm.io, to replace or augment our current Tailscale backend.
As I was experimenting with this idea I quickly hit a critical limitation of unclear purpose: connection is not allowed to port 80 and 443. Port 25 as well, but that is not a problem and completely acceptable.
Now, the recommended solution is to "simply" use fetch, but this cannot work in our scenario, especially in the case of 443 / HTTPS.
The virtualized applications inside WebVM will send a TLS encoded stream over port 443, and it is not possible (without implementing a full MITM) to convert this stream into a fetch request.
I'd like to better understand why port 80 and 443 are disallowed and if there are plans to lift this serious limitation.
As I was experimenting with this idea I quickly hit a critical limitation of unclear purpose: connection is not allowed to port 80 and 443. Port 25 as well, but that is not a problem and completely acceptable.
Now, the recommended solution is to "simply" use fetch, but this cannot work in our scenario, especially in the case of 443 / HTTPS.
The virtualized applications inside WebVM will send a TLS encoded stream over port 443, and it is not possible (without implementing a full MITM) to convert this stream into a fetch request.
I'd like to better understand why port 80 and 443 are disallowed and if there are plans to lift this serious limitation.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,942Members
Resources
Similar Threads
Was this page helpful?
