🐛 BUG: Wrangler redirects to https://www.localhost:8787
See original GitHub issueWhat version of Wrangler
are you using?
0.0.0-893830aa
What operating system are you using?
macOS
Describe the Bug
When running wrangler dev
(no args) Wrangler says it’s running on http://0.0.0.0:8787
but upon requesting any path it returns a 301 redirect to https://www.localhost:8787
.
I’m definitely not returning this redirect, this is Wrangler.
This does not happen using --local
.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
[Question] How to Debug Workers on a Subdomain
When I visit localhost:8787 wrangler redirects me to my root domain, without triggering the worker. I have tried to visit foo.localhost:8787 ...
Read more >Issue 444479: All localhost sites redirect to HTTPS ... - Monorail
After running any localhost site under HTTPS, all locahost sites automatically redirect to HTTPS under Chrome. Locahost sites are differentiated by port number, ......
Read more >@cloudflare/wrangler | Yarn - Package Manager
wrangler dev is a local proxy server to Cloudflare's preview service, allowing you to automatically re-build and preview your application on localhost ....
Read more >Overcoming a podcast app-bug using Cloudflare Workers
Which then lets you shoot requests to the worker as if it were hosted, but on your local machine, on http://localhost:8787 . The...
Read more >Wrangler | Noise
Post Syndicated from Brendan Coll original https://blog.cloudflare.com/improving-workers-types/. Improving Workers TypeScript support: accuracy, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
After discussing this with the team, we’re treating this as a bug, and will have a fix up shortly to handle
zone_name
the same aszone_id
This is the behaviour, but only if
zone_id
is used rather thanzone_name
(i.e.routes = [{ pattern = "subdomain.example.com/*", zone_id = "12345..." }]
. However, that’s not super intuitive, and so I’ll re-open this for discussion.