You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When upgrading a package, it would be better for security if HTTP URLs were upgraded to HTTPS. That way package maintainers wouldn't necessarily need to know or care if they use an HTTP or HTTPS URL, and winget users would get the security benefit.
This could be achieved by making an HTTP HEAD request to the HTTPS equivalent any HTTP URLs, and if a 200 is returned, the URL could be upgraded HTTPS transparently.
I've made it so that if the URL's scheme is HTTP, it will update it to HTTPS and send a HEAD request to the new URL. If the request fails or returns an error (status codes 400-599), it will change the scheme back to HTTP.
What would you like to see changed/added?
When upgrading a package, it would be better for security if HTTP URLs were upgraded to HTTPS. That way package maintainers wouldn't necessarily need to know or care if they use an HTTP or HTTPS URL, and winget users would get the security benefit.
This could be achieved by making an HTTP HEAD request to the HTTPS equivalent any HTTP URLs, and if a 200 is returned, the URL could be upgraded HTTPS transparently.
See also: microsoft/winget-pkgs#90273
The text was updated successfully, but these errors were encountered: