Feedback

Author: ManickaP

xml/System.Net/ServicePoint.xml

@@ -196,7 +196,7 @@
  Some load balancing techniques require a client to use a specific local IP address and port number, rather than <xref:System.Net.IPAddress.Any?displayProperty=nameWithType> (or <xref:System.Net.IPAddress.IPv6Any?displayProperty=nameWithType> for Internet Protocol Version 6) and an ephemeral port. Your <xref:System.Net.ServicePoint.BindIPEndPointDelegate> can satisfy this requirement.
 
 > [!NOTE]
->  On modern .NET, <xref:System.Net.HttpWebRequest> uses <xref:System.Net.Http.SocketsHttpHandler.ConnectCallback?displayProperty=nameWithType> to bind the underlying socket to the endpoint from this delegate.
+>  Since .NET 9, <xref:System.Net.HttpWebRequest> uses <xref:System.Net.Http.SocketsHttpHandler.ConnectCallback?displayProperty=nameWithType> to bind the underlying socket to the endpoint from this delegate.
 
  ]]></format>
         </remarks>
@@ -259,7 +259,7 @@
 Although a <xref:System.Net.ServicePoint> object can make multiple connections to an Internet resource, it can maintain only one certificate.
 
 > [!NOTE]
->  On modern .NET, returns the remote certificate retrieved via <xref:System.Net.Security.SslClientAuthenticationOptions.RemoteCertificateValidationCallback> on <xref:System.Net.Http.SocketsHttpHandler.SslOptions?displayProperty=nameWithType>.
+>  Since .NET 9, returns the remote certificate retrieved via <xref:System.Net.Security.SslClientAuthenticationOptions.RemoteCertificateValidationCallback> on <xref:System.Net.Http.SocketsHttpHandler.SslOptions?displayProperty=nameWithType>.
 
 ## Examples
  The following code example displays the value of this property.
@@ -324,7 +324,7 @@ Although a <xref:System.Net.ServicePoint> object can make multiple connections t
 ## Remarks
 
 > [!NOTE]
->  On modern .NET, this property is not implemented.
+>  Since .NET 9, this property is not implemented.
 
 ## Examples
  The following code example displays the value of this property.
@@ -455,7 +455,7 @@ Although a <xref:System.Net.ServicePoint> object can make multiple connections t
 
 
 > [!NOTE]
->  On modern .NET, this property maps to <xref:System.Net.Http.SocketsHttpHandler.PooledConnectionLifetime?displayProperty=nameWithType>. However, handlers are not being reused between requests so it doesn't have any meaningful impact.
+>  Since .NET 9, this property maps to <xref:System.Net.Http.SocketsHttpHandler.PooledConnectionLifetime?displayProperty=nameWithType>. However, handlers are not being reused between requests so it doesn't have any meaningful impact.
 
 
 ## Examples
@@ -523,7 +523,7 @@ Although a <xref:System.Net.ServicePoint> object can make multiple connections t
  The <xref:System.Net.ServicePoint.ConnectionLimit> property sets the maximum number of connections that the <xref:System.Net.ServicePoint> object can make to an Internet resource. The value of the <xref:System.Net.ServicePoint.ConnectionLimit> property is set to the value of the <xref:System.Net.ServicePointManager.DefaultConnectionLimit?displayProperty=nameWithType> property when the <xref:System.Net.ServicePoint> object is created; subsequent changes to <xref:System.Net.ServicePointManager.DefaultConnectionLimit> have no effect on existing <xref:System.Net.ServicePoint> objects.
 
 > [!NOTE]
->  On modern .NET, this property maps to <xref:System.Net.Http.SocketsHttpHandler.MaxConnectionsPerServer?displayProperty=nameWithType>. However, handlers are not being reused between requests so it doesn't have any meaningful impact.
+>  Since .NET 9, this property maps to <xref:System.Net.Http.SocketsHttpHandler.MaxConnectionsPerServer?displayProperty=nameWithType>. However, handlers are not being reused between requests so it doesn't have any meaningful impact.
 
 
 ## Examples
@@ -658,7 +658,7 @@ Although a <xref:System.Net.ServicePoint> object can make multiple connections t
  The <xref:System.Net.ServicePoint.CurrentConnections> property contains the number of open Internet connections associated with this <xref:System.Net.ServicePoint> object. The value of <xref:System.Net.ServicePoint.CurrentConnections> cannot exceed that of <xref:System.Net.ServicePoint.ConnectionLimit>.
 
 > [!NOTE]
->  On modern .NET, this property is not implemented.
+>  Since .NET 9, this property is not implemented.
 
 ## Examples
  The following code example uses the <xref:System.Net.ServicePoint.CurrentConnections> property to determine the number of open Internet connections associated with this <xref:System.Net.ServicePoint> object.
@@ -740,7 +740,7 @@ Although a <xref:System.Net.ServicePoint> object can make multiple connections t
  The Expect 100-Continue behavior is fully described in IETF RFC 2616 Section 10.1.1.
 
 > [!NOTE]
->  On modern .NET, this property sets <xref:System.Net.Http.Headers.HttpRequestHeaders.ExpectContinue?displayProperty=nameWithType> on the <xref:System.Net.Http.HttpRequestMessage.Headers?displayProperty=nameWithType>.
+>  Since .NET 9, this property sets <xref:System.Net.Http.Headers.HttpRequestHeaders.ExpectContinue?displayProperty=nameWithType> on the <xref:System.Net.Http.HttpRequestMessage.Headers?displayProperty=nameWithType>.
 
 ## Examples
  The following code example displays the value of this property.
@@ -915,7 +915,7 @@ The `GetHashCode` method returns a hash code of this instance. This value can be
  When the <xref:System.Net.ServicePoint.MaxIdleTime> for a connection associated with a <xref:System.Net.ServicePoint> is exceeded, the connection remains open until the application tries to use the connection. At that time, the Framework closes the connection and creates a new connection to the remote host.
 
 > [!NOTE]
->  On modern .NET, this property maps to <xref:System.Net.Http.SocketsHttpHandler.PooledConnectionIdleTimeout?displayProperty=nameWithType>. However, handlers are not being reused between requests so it doesn't have any meaningful impact.
+>  Since .NET 9, this property maps to <xref:System.Net.Http.SocketsHttpHandler.PooledConnectionIdleTimeout?displayProperty=nameWithType>. However, handlers are not being reused between requests so it doesn't have any meaningful impact.
 
 ## Examples
  The following code example uses the <xref:System.Net.ServicePoint.MaxIdleTime> property to set and retrieve the <xref:System.Net.ServicePoint> idle time.
@@ -980,7 +980,7 @@ The `GetHashCode` method returns a hash code of this instance. This value can be
  The HTTP protocol versions are HTTP/1.0 and HTTP/1.1.
 
 > [!NOTE]
->  On modern .NET, this property returns <xref:System.Net.HttpWebRequest.ProtocolVersion?displayProperty=nameWithType>.
+>  Since .NET 9, this property returns <xref:System.Net.HttpWebRequest.ProtocolVersion?displayProperty=nameWithType>.
 
 ## Examples
  The following code example displays the value of this property.
@@ -1048,7 +1048,7 @@ The `GetHashCode` method returns a hash code of this instance. This value can be
  For additional information, see <xref:System.Net.Sockets.Socket.ReceiveBufferSize>.
 
 > [!NOTE]
->  On modern .NET, <xref:System.Net.HttpWebRequest> uses <xref:System.Net.Http.SocketsHttpHandler.ConnectCallback?displayProperty=nameWithType> to set <xref:System.Net.Sockets.Socket.ReceiveBufferSize?displayProperty=nameWithType> to the value of this property.
+>  Since .NET 9, <xref:System.Net.HttpWebRequest> uses <xref:System.Net.Http.SocketsHttpHandler.ConnectCallback?displayProperty=nameWithType> to set <xref:System.Net.Sockets.Socket.ReceiveBufferSize?displayProperty=nameWithType> to the value of this property.
 
 ## Examples
  The following code example sets the value of this property.
@@ -1130,7 +1130,7 @@ The `GetHashCode` method returns a hash code of this instance. This value can be
  If a TCP connection is dropped as the result of keep-alives, a <xref:System.Net.Sockets.SocketError> of <xref:System.Net.Sockets.SocketError.NetworkReset> is returned to any calls in progress on the socket, and any subsequent calls will fail with a <xref:System.Net.Sockets.SocketError> of <xref:System.Net.Sockets.SocketError.NotConnected>.
 
 > [!NOTE]
->  On modern .NET, <xref:System.Net.HttpWebRequest> uses <xref:System.Net.Http.SocketsHttpHandler.ConnectCallback?displayProperty=nameWithType> to set TCP keep alive options on the underlying socket to the values provided to this method.
+>  Since .NET 9, <xref:System.Net.HttpWebRequest> uses <xref:System.Net.Http.SocketsHttpHandler.ConnectCallback?displayProperty=nameWithType> to set TCP keep alive options on the underlying socket to the values provided to this method.
 
  ]]></format>
         </remarks>
@@ -1190,7 +1190,7 @@ The `GetHashCode` method returns a hash code of this instance. This value can be
  Pipelining is described in detail in IETF RFC 2616 section 8.1.2.2.
 
 > [!NOTE]
->  On modern .NET, this property is not implemented.
+>  Since .NET 9, this property is not implemented.
 
 ## Examples
  The following code example displays the value of this property.
@@ -1268,7 +1268,7 @@ The `GetHashCode` method returns a hash code of this instance. This value can be
  The Nagle algorithm is fully described in IETF RFC 896.
 
 > [!NOTE]
->  On modern .NET, <xref:System.Net.HttpWebRequest> uses <xref:System.Net.Http.SocketsHttpHandler.ConnectCallback?displayProperty=nameWithType> to set <xref:System.Net.Sockets.Socket.NoDelay?displayProperty=nameWithType> to the opposite value than this property.
+>  Since .NET 9, <xref:System.Net.HttpWebRequest> uses <xref:System.Net.Http.SocketsHttpHandler.ConnectCallback?displayProperty=nameWithType> to set <xref:System.Net.Sockets.Socket.NoDelay?displayProperty=nameWithType> to the opposite value than this property.
 
 ## Examples
  The following code example displays the value of this property.

xml/System.Net/ServicePointManager.xml

@@ -192,7 +192,7 @@
  When the <xref:System.Net.ServicePointManager.CheckCertificateRevocationList%2A> is `true`, the certificate is checked against the certificate authority revocation list, as part of the certificate validation process. Its default value is `false`.
 
 > [!NOTE]
->  On modern .NET, this property maps to <xref:System.Net.Security.SslClientAuthenticationOptions.CertificateRevocationCheckMode> on <xref:System.Net.Http.SocketsHttpHandler.SslOptions?displayProperty=nameWithType>.
+>  Since .NET 9, this property maps to <xref:System.Net.Security.SslClientAuthenticationOptions.CertificateRevocationCheckMode> on <xref:System.Net.Http.SocketsHttpHandler.SslOptions?displayProperty=nameWithType>.
 
 ## Examples
  The following code example sets this property.
@@ -265,7 +265,7 @@
 >  Any changes to the <xref:System.Net.ServicePointManager.DefaultConnectionLimit%2A> property affect both HTTP 1.0 and HTTP 1.1 connections. It is not possible to separately alter the connection limit for HTTP 1.0 and HTTP 1.1 protocols.
 
 > [!NOTE]
->  On modern .NET, this property maps to <xref:System.Net.Http.SocketsHttpHandler.MaxConnectionsPerServer?displayProperty=nameWithType> unless overridden by <xref:System.Net.ServicePoint.ConnectionLimit?displayProperty=nameWithType>. However, handlers are not being reused between requests so it doesn't have any meaningful impact.
+>  Since .NET 9, this property maps to <xref:System.Net.Http.SocketsHttpHandler.MaxConnectionsPerServer?displayProperty=nameWithType> unless overridden by <xref:System.Net.ServicePoint.ConnectionLimit?displayProperty=nameWithType>. However, handlers are not being reused between requests so it doesn't have any meaningful impact.
 
 ## Examples
  The following code example sets this property.
@@ -423,7 +423,7 @@
 ## Remarks
 
 > [!NOTE]
->  On modern .NET, this property is not implemented.
+>  Since .NET 9, this property is not implemented.
 
 ## Examples
  The following code example sets this property.
@@ -484,7 +484,7 @@
  When more than one IP address is associated with a host name, a DNS resolution normally returns only the first IP address. If you set this property to `true`, then subsequent DNS resolutions will cycle through all available IP addresses for a particular host. This option is useful when a service uses DNS as a load balancing mechanism between servers or server clusters.
 
 > [!NOTE]
->  On modern .NET, this property is not implemented.
+>  Since .NET 9, this property is not implemented.
 
 ## Examples
  The following code example sets this property.
@@ -551,7 +551,7 @@
  The use of the Null cipher is required when the encryption policy is set to <xref:System.Net.Security.EncryptionPolicy.NoEncryption?displayProperty=nameWithType>.
 
 > [!NOTE]
->  On modern .NET, this property is not implemented.
+>  Since .NET 9, this property is not implemented.
 
  ]]></format>
         </remarks>
@@ -619,7 +619,7 @@
  The Expect 100-Continue behavior is fully described in IETF RFC 2616 Section 10.1.1.
 
 > [!NOTE]
->  On modern .NET, this property sets <xref:System.Net.Http.Headers.HttpRequestHeaders.ExpectContinue?displayProperty=nameWithType> on the <xref:System.Net.Http.HttpRequestMessage.Headers?displayProperty=nameWithType> unless overridden by <xref:System.Net.ServicePoint.Expect100Continue?displayProperty=nameWithType>.
+>  Since .NET 9, this property sets <xref:System.Net.Http.Headers.HttpRequestHeaders.ExpectContinue?displayProperty=nameWithType> on the <xref:System.Net.Http.HttpRequestMessage.Headers?displayProperty=nameWithType> unless overridden by <xref:System.Net.ServicePoint.Expect100Continue?displayProperty=nameWithType>.
 
 ## Examples
  The following code example sets this property.
@@ -917,7 +917,7 @@
  After a <xref:System.Net.ServicePoint> object has been idle for the time specified in <xref:System.Net.ServicePoint.MaxIdleTime%2A>, it is eligible for garbage collection. A <xref:System.Net.ServicePoint> object is idle when the list of connections associated with the <xref:System.Net.ServicePoint> object is empty.
 
 > [!NOTE]
->  On modern .NET, this property maps to <xref:System.Net.Http.SocketsHttpHandler.PooledConnectionIdleTimeout?displayProperty=nameWithType> unless overridden by <xref:System.Net.ServicePoint.MaxIdleTime?displayProperty=nameWithType>. However, handlers are not being reused between requests so it doesn't have any meaningful impact.
+>  Since .NET 9, this property maps to <xref:System.Net.Http.SocketsHttpHandler.PooledConnectionIdleTimeout?displayProperty=nameWithType> unless overridden by <xref:System.Net.ServicePoint.MaxIdleTime?displayProperty=nameWithType>. However, handlers are not being reused between requests so it doesn't have any meaningful impact.
 
 ## Examples
  The following code example sets this property.
@@ -987,7 +987,7 @@
  When you reduce the <xref:System.Net.ServicePointManager.MaxServicePoints%2A> property below the number of <xref:System.Net.ServicePoint> objects currently in existence, the <xref:System.Net.ServicePointManager> deletes the <xref:System.Net.ServicePoint> objects with the longest idle times. If the number of <xref:System.Net.ServicePoint> objects with active connections is greater than the value of <xref:System.Net.ServicePointManager.MaxServicePoints%2A>, the <xref:System.Net.ServicePointManager> object deletes the <xref:System.Net.ServicePoint> objects as they become idle.
 
 > [!NOTE]
->  On modern .NET, this property is not implemented.
+>  Since .NET 9, this property is not implemented.
 
 ## Examples
  The following code example sets this property.
@@ -1049,7 +1049,7 @@
  The default value is `false`.
 
 > [!NOTE]
->  On modern .NET, this property is not implemented.
+>  Since .NET 9, this property is not implemented.
 
  ]]></format>
         </remarks>
@@ -1118,7 +1118,7 @@ For versions of the .NET Framework through the .NET Framework 4.6.2, no default
  Developers may want to opt out of this behavior in order to maintain interoperability with their existing SSL3 services OR TLS w/ RC4 services. [This article](https://support.microsoft.com/kb/3069494) explains how to modify your code so that the new behavior is disabled.
 
 > [!NOTE]
->  On modern .NET, this property maps to <xref:System.Net.Security.SslClientAuthenticationOptions.EnabledSslProtocols> on <xref:System.Net.Http.SocketsHttpHandler.SslOptions?displayProperty=nameWithType>.
+>  Since .NET 9, this property maps to <xref:System.Net.Security.SslClientAuthenticationOptions.EnabledSslProtocols> on <xref:System.Net.Http.SocketsHttpHandler.SslOptions?displayProperty=nameWithType>.
 
  ]]></format>
         </remarks>
@@ -1186,7 +1186,7 @@ In other words, you can attach multiple delegates, and they all get a callback f
 Each callback returns a value that indicates whether the certificate is accepted or not; however, only the value from the last delegate is respected.
 
 > [!NOTE]
->  On modern .NET, this property maps to <xref:System.Net.Security.SslClientAuthenticationOptions.RemoteCertificateValidationCallback> on <xref:System.Net.Http.SocketsHttpHandler.SslOptions?displayProperty=nameWithType>.
+>  Since .NET 9, this property maps to <xref:System.Net.Security.SslClientAuthenticationOptions.RemoteCertificateValidationCallback> on <xref:System.Net.Http.SocketsHttpHandler.SslOptions?displayProperty=nameWithType>.
 
  ]]></format>
         </remarks>
@@ -1259,7 +1259,7 @@ Each callback returns a value that indicates whether the certificate is accepted
  If a TCP connection is dropped as the result of keep-alives, a <xref:System.Net.Sockets.SocketError> of <xref:System.Net.Sockets.SocketError.NetworkReset> is returned to any calls in progress on the socket, and any subsequent calls will fail with a <xref:System.Net.Sockets.SocketError> of <xref:System.Net.Sockets.SocketError.NotConnected>.
 
 > [!NOTE]
->  On modern .NET, <xref:System.Net.HttpWebRequest> uses <xref:System.Net.Http.SocketsHttpHandler.ConnectCallback?displayProperty=nameWithType> to set TCP keep alive options on the underlying socket to the values provided to this method.
+>  Since .NET 9, <xref:System.Net.HttpWebRequest> uses <xref:System.Net.Http.SocketsHttpHandler.ConnectCallback?displayProperty=nameWithType> to set TCP keep alive options on the underlying socket to the values provided to this method.
 
  ]]></format>
         </remarks>
@@ -1319,7 +1319,7 @@ Each callback returns a value that indicates whether the certificate is accepted
  The Nagle algorithm is fully described in IETF RFC 896.
 
 > [!NOTE]
->  On modern .NET, <xref:System.Net.HttpWebRequest> uses <xref:System.Net.Http.SocketsHttpHandler.ConnectCallback?displayProperty=nameWithType> to set <xref:System.Net.Sockets.Socket.NoDelay?displayProperty=nameWithType> to the opposite value than this property.
+>  Since .NET 9, <xref:System.Net.HttpWebRequest> uses <xref:System.Net.Http.SocketsHttpHandler.ConnectCallback?displayProperty=nameWithType> to set <xref:System.Net.Sockets.Socket.NoDelay?displayProperty=nameWithType> to the opposite value than this property.
 
 ## Examples
  The following code example sets this property.