-
Notifications
You must be signed in to change notification settings - Fork 803
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Bug Report — Runtime APIs: Get an incorrect Location param when using Response.redirect #5221
Comments
Hey! 👋 Thanks for raising this. I'm able to reproduce it locally. This is very likely an issue with |
Im experimenting the same issue From what I found, seem to have been introduced in packages/wrangler/templates/startDevWorker/ProxyWorker.ts I start the worker like this: devsite.localg:33667: is my origin, a node express server --host devsite.localg: I access my worker from same domain devsite.localg:8787 Behavior: with the script above is converted to: this is because of: there is the value I have for (from , to) { "http://devsite.localg:8787/destination" |
When I use
wrangler dev --host localhost:3343
for local development, I want to get a redirect response. But my port number was mishandled and I can’t get the redirect address I’m hoping for. I'm sure it's not the browser's behavior.wrangler version:
^3.32.0
Example
The text was updated successfully, but these errors were encountered: