Upgrade links to https (#2425)

* change xmlsoap.org links to https

* change codeproject.com links to https

* change ietf.org links to https

* change w3 links to https and working path

* change additional instances to https

Author: dsychin

includes/wif-wstrust-ref-md.md

@@ -1 +1 @@
-For more information about the element that this class represents, see the WS-Trust specification that applies to your scenario: [WS-Trust February 2005](http://schemas.xmlsoap.org/ws/2005/02/trust/), [WS-Trust 1.3](https://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3-os.html), or [WS-Trust 1.4](https://docs.oasis-open.org/ws-sx/ws-trust/v1.4/os/ws-trust-1.4-spec-os.html).
+For more information about the element that this class represents, see the WS-Trust specification that applies to your scenario: [WS-Trust February 2005](https://schemas.xmlsoap.org/ws/2005/02/trust/), [WS-Trust 1.3](https://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3-os.html), or [WS-Trust 1.4](https://docs.oasis-open.org/ws-sx/ws-trust/v1.4/os/ws-trust-1.4-spec-os.html).

xml/System.Collections.Specialized/INotifyCollectionChanged.xml

@@ -51,9 +51,9 @@
   
  If you have an advanced scenario and want to implement your own collection, consider using <xref:System.Collections.IList>, which provides a non-generic collection of objects that can be individually accessed by index and provides the best performance.  
   
- ]]></format>
+ ]]>      </format>
     </remarks>
-    <related type="ExternalDocumentation" href="http://www.codeproject.com/Articles/1004644/ObservableCollection-Simply-Explained">ObservableCollection Simply Explained</related>
+    <related type="ExternalDocumentation" href="https://www.codeproject.com/Articles/1004644/ObservableCollection-Simply-Explained">ObservableCollection Simply Explained</related>
   </Docs>
   <Members>
     <Member MemberName="CollectionChanged">
@@ -99,7 +99,7 @@
 ## Remarks  
  The event handler receives an argument of type <xref:System.Collections.Specialized.NotifyCollectionChangedEventArgs>,which contains data that is related to this event.  
   
- ]]></format>
+ ]]>          </format>
         </remarks>
       </Docs>
     </Member>

xml/System.Collections.Specialized/NotifyCollectionChangedAction.xml

@@ -42,7 +42,7 @@
     <remarks>To be added.</remarks>
     <altmember cref="T:System.Collections.Specialized.INotifyCollectionChanged" />
     <altmember cref="T:System.Collections.Specialized.NotifyCollectionChangedEventArgs" />
-    <related type="ExternalDocumentation" href="http://www.codeproject.com/Articles/1004644/ObservableCollection-Simply-Explained">ObservableCollection Simply Explained</related>
+    <related type="ExternalDocumentation" href="https://www.codeproject.com/Articles/1004644/ObservableCollection-Simply-Explained">ObservableCollection Simply Explained</related>
   </Docs>
   <Members>
     <Member MemberName="Add">

xml/System.IO.Packaging/PackagePart.xml

@@ -95,7 +95,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- `partUri` must be valid <xref:System.IO.Packaging.PackagePart> [!INCLUDE[TLA2#tla_uri](~/includes/tla2sharptla-uri-md.md)] formed in accordance with the [RFC 3986](http://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification and the [Open Packaging Conventions](https://go.microsoft.com/fwlink/?LinkID=71255) specification.  
+ `partUri` must be valid <xref:System.IO.Packaging.PackagePart> [!INCLUDE[TLA2#tla_uri](~/includes/tla2sharptla-uri-md.md)] formed in accordance with the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification and the [Open Packaging Conventions](https://go.microsoft.com/fwlink/?LinkID=71255) specification.  
   
  Use this constructor when the <xref:System.IO.Packaging.PackagePart.ContentType%2A> of the part is not immediately known and will be set later when <xref:System.IO.Packaging.Package.CreatePart%2A> is called.  
   
@@ -148,7 +148,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- `partUri` must be valid <xref:System.IO.Packaging.PackagePart> [!INCLUDE[TLA2#tla_uri](~/includes/tla2sharptla-uri-md.md)] formed in accordance with the [RFC 3986](http://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification and the [Open Packaging Conventions](https://go.microsoft.com/fwlink/?LinkID=71255) specification.  
+ `partUri` must be valid <xref:System.IO.Packaging.PackagePart> [!INCLUDE[TLA2#tla_uri](~/includes/tla2sharptla-uri-md.md)] formed in accordance with the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification and the [Open Packaging Conventions](https://go.microsoft.com/fwlink/?LinkID=71255) specification.  
   
  By default, the <xref:System.IO.Packaging.PackagePart.CompressionOption%2A> property of the part is initialized to <xref:System.IO.Packaging.CompressionOption.NotCompressed>.  
   
@@ -211,7 +211,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- `partUri` must be valid <xref:System.IO.Packaging.PackagePart> [!INCLUDE[TLA2#tla_uri](~/includes/tla2sharptla-uri-md.md)] formed in accordance with the [RFC 3986](http://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification and the [Open Packaging Conventions](https://go.microsoft.com/fwlink/?LinkID=71255) specification.  
+ `partUri` must be valid <xref:System.IO.Packaging.PackagePart> [!INCLUDE[TLA2#tla_uri](~/includes/tla2sharptla-uri-md.md)] formed in accordance with the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification and the [Open Packaging Conventions](https://go.microsoft.com/fwlink/?LinkID=71255) specification.  
   
  `contentType` must be a [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] type formed in accordance with the [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616.html) *Hypertext Transfer Protocol - HTTP*, Section 3.7.  The following table shows an example of the content [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] types used in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] documents.  
   
@@ -430,11 +430,11 @@
   
  The target of a relationship cannot be another relationship.  
   
- If `targetMode` is specified as <xref:System.IO.Packaging.TargetMode.Internal>, `targetUri` must be a relative URI that is formed in accordance with the [RFC 3986](http://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  The internal relative URI can be either an absolute path that starts with a forward slash ("/") character such as "/page1.xaml" or "/images/picture4.jpg", or a relative path such as "../imagespicture1.jpg" that resolves against the package root ("/") as the base URI.  
+ If `targetMode` is specified as <xref:System.IO.Packaging.TargetMode.Internal>, `targetUri` must be a relative URI that is formed in accordance with the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  The internal relative URI can be either an absolute path that starts with a forward slash ("/") character such as "/page1.xaml" or "/images/picture4.jpg", or a relative path such as "../imagespicture1.jpg" that resolves against the package root ("/") as the base URI.  
   
- If `targetMode` is specified as <xref:System.IO.Packaging.TargetMode.External>, `targetUri` can be either an absolute or relative URI formed in accordance with the [RFC 3986](http://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  "http://www.microsoft.com/page2.xml" is an example of an absolute URI that references an external target resource "page2.xml".  "images/picture1.jpg" is an example of a relative URI that also references an external target resource "1.jpg" but which resolves against the URI of the package itself.  
+ If `targetMode` is specified as <xref:System.IO.Packaging.TargetMode.External>, `targetUri` can be either an absolute or relative URI formed in accordance with the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  "https://www.microsoft.com/page2.xml" is an example of an absolute URI that references an external target resource "page2.xml".  "images/picture1.jpg" is an example of a relative URI that also references an external target resource "1.jpg" but which resolves against the URI of the package itself.  
   
- `relationshipType` must be a [!INCLUDE[TLA2#tla_uri](~/includes/tla2sharptla-uri-md.md)] that is formed according to the [RFC 3986](http://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  Different package types can define different part-level relationship types.  The following table shows the part-level `relationshipType` URIs defined for documents that conform to the *Open XML Paper Specification (XPS)*.  
+ `relationshipType` must be a [!INCLUDE[TLA2#tla_uri](~/includes/tla2sharptla-uri-md.md)] that is formed according to the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  Different package types can define different part-level relationship types.  The following table shows the part-level `relationshipType` URIs defined for documents that conform to the *Open XML Paper Specification (XPS)*.  
   
 |XPS Document Part-Level Relationship|Relationship Type URI|  
 |-------------------------------------------|---------------------------|  
@@ -528,11 +528,11 @@
   
  The target of a relationship cannot be another relationship.  
   
- If `targetMode` is specified as <xref:System.IO.Packaging.TargetMode.Internal>, `targetUri` must be a relative URI that is formed in accordance with the [RFC 3986](http://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  The internal relative URI can be either an absolute path that starts with a forward slash ("/") character such as "/page1.xaml" or "/images/picture4.jpg", or a relative path such as "../imagespicture1.jpg" that resolves against the package root ("/") as the base URI.  
+ If `targetMode` is specified as <xref:System.IO.Packaging.TargetMode.Internal>, `targetUri` must be a relative URI that is formed in accordance with the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  The internal relative URI can be either an absolute path that starts with a forward slash ("/") character such as "/page1.xaml" or "/images/picture4.jpg", or a relative path such as "../imagespicture1.jpg" that resolves against the package root ("/") as the base URI.  
   
- If `targetMode` is specified as <xref:System.IO.Packaging.TargetMode.External>, `targetUri` can be either an absolute or relative URI formed in accordance with the [RFC 3986](http://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  "http://www.microsoft.com/page2.xml" is an example of an absolute URI that references an external target resource "page2.xml".  "images/picture1.jpg" is an example of a relative URI that also references an external target resource "1.jpg" but which resolves against the URI of the package itself.  
+ If `targetMode` is specified as <xref:System.IO.Packaging.TargetMode.External>, `targetUri` can be either an absolute or relative URI formed in accordance with the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  "https://www.microsoft.com/page2.xml" is an example of an absolute URI that references an external target resource "page2.xml".  "images/picture1.jpg" is an example of a relative URI that also references an external target resource "1.jpg" but which resolves against the URI of the package itself.  
   
- `relationshipType` must be a [!INCLUDE[TLA2#tla_uri](~/includes/tla2sharptla-uri-md.md)] that is formed according to the [RFC 3986](http://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  Different package types can define different part-level relationship types.  The following table shows the part-level `relationshipType` URIs defined for documents that conform to the *Open XML Paper Specification (XPS)*.  
+ `relationshipType` must be a [!INCLUDE[TLA2#tla_uri](~/includes/tla2sharptla-uri-md.md)] that is formed according to the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  Different package types can define different part-level relationship types.  The following table shows the part-level `relationshipType` URIs defined for documents that conform to the *Open XML Paper Specification (XPS)*.  
   
 |XPS Document Part-Level Relationship|Relationship Type URI|  
 |-------------------------------------------|---------------------------|  

xml/System.IdentityModel.Protocols.WSTrust/EndpointReference.xml

@@ -21,7 +21,7 @@
 ## Remarks  
  The wsa:EndpointReference element can be used in wst:OnBehalfOf and wp:AppliesTo elements inside of a wsp:RequestSecurityToken element to specify an endpoint reference.  
   
- Supports either the [WS-Addressing standard schema namespace](http://schemas.xmlsoap.org/ws/2004/08/addressing) or the [WS-Addressing 1.0 schema namespace](https://www.w3.org/2005/08/addressing) when reading. On write only the [WS-Addressing 1.0 namespace](https://www.w3.org/2005/08/addressing) is supported.  
+ Supports either the [WS-Addressing standard schema namespace](https://schemas.xmlsoap.org/ws/2004/08/addressing) or the [WS-Addressing 1.0 schema namespace](https://www.w3.org/2005/08/addressing) when reading. On write only the [WS-Addressing 1.0 namespace](https://www.w3.org/2005/08/addressing) is supported.  
   
  For more information about the wsa:EndpointReference element, see the Web Services Addressing - Core specification. For more information about its use in WS-Trust protocols, see the version of the WS-Trust specification that applies to your scenario.  
   
@@ -95,7 +95,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Reads the contents of the wsa:EndpointReference element and returns an <xref:System.IdentityModel.Protocols.WSTrust.EndpointReference> object. The WS-Addressing namespace can be either the [WS-Addressing standard schema](http://schemas.xmlsoap.org/ws/2004/08/addressing) or the [WS-Addressing 1.0 standard schema](https://www.w3.org/2005/08/addressing). The wsa:Address element must be the first child element of the wsa:EndpointReference element. The <xref:System.IdentityModel.Protocols.WSTrust.EndpointReference.Uri%2A> property in the returned <xref:System.IdentityModel.Protocols.WSTrust.EndpointReference> is set to the URI specified by the wsa:Address element. All other child elements are added to the <xref:System.IdentityModel.Protocols.WSTrust.EndpointReference.Details%2A> collection.  
+ Reads the contents of the wsa:EndpointReference element and returns an <xref:System.IdentityModel.Protocols.WSTrust.EndpointReference> object. The WS-Addressing namespace can be either the [WS-Addressing standard schema](https://schemas.xmlsoap.org/ws/2004/08/addressing) or the [WS-Addressing 1.0 standard schema](https://www.w3.org/2005/08/addressing). The wsa:Address element must be the first child element of the wsa:EndpointReference element. The <xref:System.IdentityModel.Protocols.WSTrust.EndpointReference.Uri%2A> property in the returned <xref:System.IdentityModel.Protocols.WSTrust.EndpointReference> is set to the URI specified by the wsa:Address element. All other child elements are added to the <xref:System.IdentityModel.Protocols.WSTrust.EndpointReference.Details%2A> collection.  
   
  ]]></format>
         </remarks>

xml/System.Net.WebSockets/WebSocket.xml

@@ -138,15 +138,15 @@
         <param name="closeStatus">Indicates the reason for closing the WebSocket connection.</param>
         <param name="statusDescription">Specifies a human readable explanation as to why the connection is closed.</param>
         <param name="cancellationToken">The token that can be used to propagate notification that operations should be canceled.</param>
-        <summary>Closes the WebSocket connection as an asynchronous operation using the close handshake defined in the <see href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-06">WebSocket protocol specification</see> section 7.</summary>
+        <summary>Closes the WebSocket connection as an asynchronous operation using the close handshake defined in the <see href="https://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-06">WebSocket protocol specification</see> section 7.</summary>
         <returns>The task object representing the asynchronous operation.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
  This operation will not block. The returned <xref:System.Threading.Tasks.Task> object will complete after the WebSocket has been closed.  
   
- This method closes the WebSocket connection using the close handshake defined in the [WebSocket protocol specification](http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-06) section 7.  
+ This method closes the WebSocket connection using the close handshake defined in the [WebSocket protocol specification](https://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-06) section 7.  
   
  ]]></format>
         </remarks>
@@ -187,7 +187,7 @@
         <param name="closeStatus">Indicates the reason for closing the WebSocket connection.</param>
         <param name="statusDescription">Allows applications to specify a human readable explanation as to why the connection is closed.</param>
         <param name="cancellationToken">The token that can be used to propagate notification that operations should be canceled.</param>
-        <summary>Initiates or completes the close handshake defined in the <see href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-06">WebSocket protocol specification section 7</see>.</summary>
+        <summary>Initiates or completes the close handshake defined in the <see href="https://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-06">WebSocket protocol specification section 7</see>.</summary>
         <returns>The task object representing the asynchronous operation.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  

xml/System.Security.Cryptography.Xml/SignedXml.xml

@@ -172,7 +172,7 @@
   
  ]]></format>
     </remarks>
-    <related type="ExternalDocumentation" href="http://www.w3.org/TR/xmldsig-bestpractices">XML Signature Best Practices</related>
+    <related type="ExternalDocumentation" href="https://www.w3.org/TR/xmldsig-bestpractices">XML Signature Best Practices</related>
   </Docs>
   <Members>
     <MemberGroup MemberName=".ctor">
@@ -1271,7 +1271,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Canonicalization methods convert an XML document to its canonical form. For more information about canonical XML, see [Canonical XML](http://www.w3.org/TR/xml-c14n) on the W3C website.  
+ Canonicalization methods convert an XML document to its canonical form. For more information about canonical XML, see [Canonical XML](https://www.w3.org/TR/xml-c14n) on the W3C website.  
   
  ]]></format>
         </remarks>
@@ -2389,7 +2389,7 @@
   
  Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG.  
   
- For more information, see the World Wide Web Consortium (W3C) specification at [http://www.w3.org/2001/04/xmlenc#sha256](http://www.w3.org/2001/04/xmlenc#sha256).  
+ For more information, see the World Wide Web Consortium (W3C) specification at [http://www.w3.org/2001/04/xmlenc#sha256](https://www.w3.org/2001/04/xmlenc#sha256).  
   
  ]]></format>
         </remarks>
@@ -2459,7 +2459,7 @@
   
  Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG.  
   
- For more information, see the World Wide Web Consortium (W3C) specification at [http://www.w3.org/2001/04/xmlenc#sha512](http://www.w3.org/2001/04/xmlenc#sha512).  
+ For more information, see the World Wide Web Consortium (W3C) specification at [http://www.w3.org/2001/04/xmlenc#sha512](https://www.w3.org/2001/04/xmlenc#sha512).  
   
  ]]></format>
         </remarks>