-
-
Notifications
You must be signed in to change notification settings - Fork 16.7k
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
4.19.0 breaks passing new URL() into res.redirect(...) #5554
Comments
Ahhhh, yep that is not covered in the tests. I can prep a patch for that. |
@kavika-1 Do you have a code snippet example of what you are doing so I can make sure this covers your case? |
Can you check the PR to ensure it would cover you? CI is failing because of #5552 but I can merge this all together for the patch if this will fix your report. |
Example Code snippet, which should be fixed with this patch, thanks!
|
Published with 4.19.1. Thanks for the quick report, this would certainly have been something lots of folks hit. |
Amazing turnaround, thanks @wesleytodd! |
Ahah nice. I was hit by this and double checked the documentation. Clearly Thanks for your reactivity! Cheers, |
Understandably, res.redirect(...) should take a string. But for years we have been successfully passing a new URL(). We can certainly fix this on our side, but wanted to give a heads-up that this change might cause others to run into the same thing.
Error ultimately is thrown here:
reponse.js:915
var lowerLoc = loc.toLowerCase();
The text was updated successfully, but these errors were encountered: