Repository navigation
'Invoke-WebRequest -SkipCertificateCheck' doesn't work with netcoreapp2.0 on Mac #3648
Description
This is because HttpClientHandler.ServerCertificateCustomValidationCallback currently doesn't work in netcoreapp2.0 on Mac at all. See the comment in https://github.com/dotnet/corefx/issues/9728 for more information.
Note that we currently have 2 tests failing in nightly run on OSX CI:
Validate Invoke-WebRequest -SkipCertificateCheck
Validate Invoke-RestMethod -SkipCertificateCheck
Error message is:
The handler does not support custom handling of certificates with this combination of libcurl (7.49.1) and its SSL backend ("SecureTransport").
Activity
SteveL-MSFT commentedon Apr 26, 2017
Joey Aiello (@joeyaiello) we should add this to Known Issues
Mark '-SkipCertificateCheck' tests pending on OSX for now (#3660)
joeyaiello commentedon May 17, 2017
Dongbo Wang (@daxian-dbw) it looks like dotnet/corefx#19709 would solve our problem as well. Could you validate that?
stephentoub commentedon May 23, 2017
Please let us know if dotnet/corefx#19941 doesn't address this need. I believe it should.
iSazonov commentedon Jun 14, 2017
Dongbo Wang (@daxian-dbw) Is the Issue fixed?
daxian-dbw commentedon Jun 14, 2017
Yes, it's fixed by #3887
daxian-dbw commentedon Jun 15, 2017
We are moving back to .NET Core 2.0.0-preview1 via PR #4026 due to regressions in the latest .NET Core 2.0.0-preview2 (dotnet/corefx#21095). So re-open this bug.
iSazonov commentedon Jun 28, 2017
Dongbo Wang (@daxian-dbw) It seems CoreFX was fixed and we can move to new version.
daxian-dbw commentedon Jun 28, 2017
Ilya (@iSazonov) I would love to, but the
2.0.0-preview3.NET CLI is broken: https://github.com/dotnet/cli/issues/7013iSazonov commentedon Jun 28, 2017
😄 Again?! It looks we near release candidate.
daxian-dbw commentedon Jun 28, 2017
Ilya (@iSazonov) I'm planning to use preview2 CLI and explicitly specify the
RuntimeFrameworkVersionto bepreview3packages. Maybe this is good in the long run so that we don't need to change the CLI we are using when we want to move to later version of .NET Core.iSazonov commentedon Jun 29, 2017
I believe it is good for us. Will this affect the use of PowerShell Core SDK by third-party developers (for binary modules)?
daxian-dbw commentedon Jun 30, 2017
This issue is fixed by #4144
Mark '-SkipCertificateCheck' tests pending on OSX for now (PowerShell…