-
-
Notifications
You must be signed in to change notification settings - Fork 61
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]: Recent change to Resolve-SystemNetWebRequest appears to have broken URL's returned for Sourceforge based Apps #669
Comments
Here is a sample of the correct URI's being returned when running Evergreen 2404.928
|
I've updated
|
Thank you very much for the very fast fix! I wasn't able to install 7-Zip and WinSCP Friday. |
Pushed to the PowerShell gallery just now |
Evergreen Version 2405.994 Something is still off for me. On Azure VMs a command like this, for 7-zip and WinSCP, always results in a 100KB exe file, that is malformed and/or broken.
Any ideas? |
The issue could be with Have I mentioned how much I dislike SourceForge? |
I have also been wondering whether Evergreen should normalise the SourceForge URLs with a single host name, instead of returning one of the mirrors each time. |
See #677 re:SourceForge |
What happened?
When running the latest version of Evergreen module (2405.959) URI's returned for Sourceforge based apps seem to be incorrect. I think this may be as a result of recent changes to Resolve-SystemNetWebRequest to add UserAgent? The Sourceforge mirror is not getting resolved. Please see verbose output below for comparison.
Version
2405.959
What PowerShell edition/s are you running Evergreen on?
Windows PowerShell
Which operating system/s are you running Evergreen on?
Windows 10+
Have you reviewed the documentation?
Verbose output
The text was updated successfully, but these errors were encountered: