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
Recently, the action fails to download OpenSSL on Windows:
openssl v3.3.1 [Approved]
openssl package files install completed. Performing other installation steps.
Attempt to get headers for https://slproweb.com/download/Win64OpenSSL-3_3_1.exe failed.
The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://slproweb.com/download/Win64OpenSSL-3_3_1.exe'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found."
Downloading openssl 64 bit
from 'https://slproweb.com/download/Win64OpenSSL-3_3_1.exe'
ERROR: The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://slproweb.com/download/Win64OpenSSL-3_3_1.exe'.
This looks like a caching or sync issue. Now it downloads the newest version 3.3.2:
openssl v3.3.2 [Approved]
openssl package files install completed. Performing other installation steps.
Downloading openssl 64 bit
from 'https://slproweb.com/download/Win64OpenSSL-3_3_2.exe'
Download of Win64OpenSSL-3_3_2.exe (216.73 MB) completed.
The problem was that choco still had the URL for the older version 3.3.1, but that archive was removed when OpenSSL was updated to 3.3.2. It seems to take a while until choco updates the URLs.
Is there a way to prevent these things from happening when a package is updated and the old version is removed?
Description
Recently, the action fails to download OpenSSL on Windows:
The URL https://slproweb.com/download/Win64OpenSSL-3_3_1.exe (OpenSSL 3.3.1) returns a 404 while https://slproweb.com/download/Win64OpenSSL-3_3_2.exe (OpenSSL 3.3.2) works.
Expected Behavior
The action should download OpenSSL without issues.
Actual Behavior
The action fails with the above error.
System (please complete the following information)
The text was updated successfully, but these errors were encountered: