HTTPS Connection Issues - Revision history

Tom at 22:39, 20 September 2024

2024-09-20T22:39:50Z

Tom: /* Net Core Console Apps */

2021-12-06T18:22:46Z

‎Net Core Console Apps

Tom: /* Set .NET to Ignore Certificate Errors */

2021-09-22T21:35:42Z

‎Set .NET to Ignore Certificate Errors

Tom: /* Set .NET to Ignore Certificate Errors */

2021-09-22T21:35:16Z

‎Set .NET to Ignore Certificate Errors

Tom: /* Get .NET to Ignore Certificate Errors */

2021-09-22T03:31:05Z

‎Get .NET to Ignore Certificate Errors

Tom: /* References */

2021-09-22T03:30:27Z

‎References

Tom: /* PowerShell Ignore SSL Errors */

2021-09-22T03:21:20Z

‎PowerShell Ignore SSL Errors

Tom: /* References */

2021-09-22T03:19:23Z

‎References

Tom: /* Context */

2020-08-11T19:45:54Z

‎Context

Tom: /* PowerShell Invoke-xxxMethod */

2020-08-11T05:48:04Z

‎PowerShell Invoke-xxxMethod

@@ Line 3: / Line 3: @@
 ==Context==
-* For HTTPS to work the certificate (and key) used to sign the TLS (SSL) connection packets must match one of the certs in the cert:\localmachiroot folder. That means that the fingerprint (hash) of the root key must match the signing key.
+* For HTTPS to work the certificate (and key) used to sign the [[TLS]] (SSL) connection packets must match one of the certs in the cert:\localmachiroot folder. That means that the fingerprint (hash) of the root key must match the signing key.
 ==Issues==
@@ Line 42: / Line 42: @@
 * [https://evotec.xyz/invoke-restmethod-the-underlying-connection-was-closed-an-unexpected-error-occurred-on-a-send-while-connecting-graph-api/ unexpected occurances]
-One common cause for this issue is a mismatch in TLS levels between the client and server. In general all sites should be (2020-07) set for tls1.1 or higher.
+One common cause for this issue is a mismatch in [[TLS]] levels between the client and server. In general all sites should be (2020-07) set for tls1.1 or higher.
 * Check with powershell Get-TlsCipherSuite    [[-Name] <String>]   [<CommonParameters>]

@@ Line 21: / Line 21: @@
 #   Test with HTTP
 #   Test with HTTPS (one-way authentication)
-#   Test with HTTPS (mutual authentication)
+#   Test with HTTPS ([[Mutual Authentication]])
 ===PowerShell Invoke-xxxMethod===

@@ Line 113: / Line 113: @@
 Mark Meuer Apr 19 '12 at 21:50
-or this way
+or this way - Call this method before you call smtpclient.Send():
   [Obsolete("Do not use this in Production code!!!",true)]
   static void NEVER_EAT_POISON_Disable_CertificateValidation()

@@ Line 112: / Line 112: @@
 This is even more useful than it may at first appear. I ran into the OP's problem while using Managed Exchanged Web Services (EWS). I thought that I could not use this answer since I didn't have access to the low-level SOAP calls that were being made by that managed library. But when I took another look at it, I realized ServicePointManager stands on its own. So,I added the above callback before initializing the ExchangeService and it worked like a charm. –
 Mark Meuer Apr 19 '12 at 21:50
 ==References==

@@ Line 102: / Line 102: @@
 </pre>
-===Get .NET to Ignore Certificate Errors===
+===Set .NET to Ignore Certificate Errors===
 Add a certificate validation handler. Returning true will allow ignoring the validation error:
@@ Line 111: / Line 111: @@
 This is even more useful than it may at first appear. I ran into the OP's problem while using Managed Exchanged Web Services (EWS). I thought that I could not use this answer since I didn't have access to the low-level SOAP calls that were being made by that managed library. But when I took another look at it, I realized ServicePointManager stands on its own. So,I added the above callback before initializing the ExchangeService and it worked like a charm. –
 Mark Meuer Apr 19 '12 at 21:50
 ==References==

← Older revision		Revision as of 03:30, 22 September 2021
Line 101:		Line 101:

	</pre>		</pre>
		+
		+	===Get .NET to Ignore Certificate Errors===
		+
		+	Add a certificate validation handler. Returning true will allow ignoring the validation error:
		+
		+	ServicePointManager
		+	.ServerCertificateValidationCallback +=
		+	(sender, cert, chain, sslPolicyErrors) => true;
		+
		+	This is even more useful than it may at first appear. I ran into the OP's problem while using Managed Exchanged Web Services (EWS). I thought that I could not use this answer since I didn't have access to the low-level SOAP calls that were being made by that managed library. But when I took another look at it, I realized ServicePointManager stands on its own. So,I added the above callback before initializing the ExchangeService and it worked like a charm. –
		+	Mark Meuer Apr 19 '12 at 21:50

	==References==		==References==

← Older revision		Revision as of 03:21, 22 September 2021
Line 61:		Line 61:

	$result = Invoke-WebRequest -Uri "https://trustregistry.us		$result = Invoke-WebRequest -Uri "https://trustregistry.us
		+
		+	<pre>
		+	StatusCode : 200
		+	StatusDescription : OK
		+	Content : <!DOCTYPE html>
		+	<html lang="en">
		+	<head>
		+	<meta charset="utf-8" />
		+	<meta name="viewport" content="width=device-width, initial-scale=1.0" />
		+	<title>Trust Registry Home - TrustRegistry</title>...
		+	RawContent : HTTP/1.1 200 OK
		+	Transfer-Encoding: chunked
		+	Content-Type: text/html; charset=utf-8
		+	Date: Wed, 22 Sep 2021 03:17:41 GMT
		+	Server: Kestrel
		+
		+	<!DOCTYPE html>
		+	<html lang="en">
		+	<head>
		+	<meta charset="...
		+	Forms : {}
		+	Headers : {[Transfer-Encoding, chunked], [Content-Type, text/html; charset=utf-8], [Date, Wed, 22 Sep 2021
		+	03:17:41 GMT], [Server, Kestrel]}
		+	Images : {@{innerHTML=; innerText=; outerHTML=<IMG class=img-responsive style="WIDTH: 90%" alt="TR is Trust
		+	Registry" src="/images/TRBanner.png" height=120>; outerText=; tagName=IMG; class=img-responsive;
		+	style=WIDTH: 90%; alt=TR is Trust Registry; src=/images/TRBanner.png; height=120}}
		+	InputFields : {}
		+	Links : {@{innerHTML=TrustRegistry; innerText=TrustRegistry; outerHTML=<A class=navbar-brand
		+	href="/?page=%2FIndex">TrustRegistry</A>; outerText=TrustRegistry; tagName=A; class=navbar-brand;
		+	href=/?page=%2FIndex}, @{innerHTML=Home; innerText=Home; outerHTML=<A class="nav-link text-dark"
		+	href="/">Home</A>; outerText=Home; tagName=A; class=nav-link text-dark; href=/},
		+	@{innerHTML=VICAL; innerText=VICAL; outerHTML=<A class="nav-link text-dark"
		+	href="/Home/Certification">VICAL</A>; outerText=VICAL; tagName=A; class=nav-link text-dark;
		+	href=/Home/Certification}, @{innerHTML=Resources; innerText=Resources; outerHTML=<A
		+	class="nav-link text-dark" href="/Home/Resources">Resources</A>; outerText=Resources; tagName=A;
		+	class=nav-link text-dark; href=/Home/Resources}...}
		+	ParsedHtml : mshtml.HTMLDocumentClass
		+	RawContentLength : 6888
		+
		+	</pre>

	==References==		==References==

← Older revision		Revision as of 19:45, 11 August 2020
Line 3:		Line 3:

	==Context==		==Context==
		+	* For HTTPS to work the certificate (and key) used to sign the TLS (SSL) connection packets must match one of the certs in the cert:\localmachiroot folder. That means that the fingerprint (hash) of the root key must match the signing key.

	==Issues==		==Issues==