workerd icon indicating copy to clipboard operation
workerd copied to clipboard

🐛 Bug Report — allow_custom_ports is not working

Open ceddybi opened this issue 4 months ago • 12 comments

According to allow-specifying-a-custom-port-when-making-a-subrequest-with-the-fetch-api

it says that setting the flag allow_custom_ports or a compatibility date greater than 2024-09-02, should allow fetch to work with custom ports for HTTPS, however settings this has no effect, you still get the warning and the api errors out

known issue with fetch() requests to custom HTTPS ports in published Workers: the custom port will be ignored when the Worker is published using the "wrangler deploy" command.

ceddybi avatar Oct 18 '24 21:10 ceddybi