Brief description of your issue
This is very similar to #326, however I have TLS 1.2 enabled and I can access the cache fine outside winget.
Steps to reproduce
C:\WINDOWS\system32>winget --version
v0.1.42241 Preview
C:\WINDOWS\system32>winget search github
Failed to open the source; try removing and re-adding it
An unexpected error occurred while executing the command:
InternetOpenUrl() failed.
0x80072efd : unknown error
C:\WINDOWS\system32>winget source list
Name Argument
-----------------------------------------
winget https://winget.azureedge.net/cache
C:\WINDOWS\system32>winget source reset --force
Resetting all sources...Done
C:\WINDOWS\system32>winget source update
Updating all sources...
Updating source: winget...
An unexpected error occurred while executing the command:
InternetOpenUrl() failed.
0x80072efd : unknown error
C:\WINDOWS\system32>winget source add --name test https://winget.azureedge.net/cache
Adding source:
test -> https://winget.azureedge.net/cache
An unexpected error occurred while executing the command:
A connection with the server could not be established
C:\WINDOWS\system32>curl https://winget.azureedge.net/cache
´╗┐<?xml version="1.0" encoding="utf-8"?><Error><Code>ResourceNotFound</Code><Message>The specified resource does not exist.
RequestId:a5bc7e36-e01e-009c-76ff-88e0ac000000
Time:2020-09-12T12:24:09.5326840Z</Message></Error>
Expected behavior
winget should function
Actual behavior
winget does not function
Environment
C:\WINDOWS\system32>winget --info
Windows Package Manager v0.1.42241 Preview
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.18362.1016
Package: Microsoft.DesktopAppInstaller v1.10.42241.0
Brief description of your issue
This is very similar to #326, however I have TLS 1.2 enabled and I can access the cache fine outside
winget.Steps to reproduce
Expected behavior
wingetshould functionActual behavior
wingetdoes not functionEnvironment