Use datatracker URLs for IETF documents rather than tools.ietf.org (#…

…3174) tools.ietf.org are being deprecated per https://mailarchive.ietf.org/arch/msg/tools-discuss/oYrAxb3KayPzZ4SNB1DVZTDPPNo/ changes generated with rg -l https://tools.ietf.org/html
mdn · Mar 16, 2021 · 48fca0c · 48fca0c
1 parent bba5e7a
commit 48fca0c
Show file tree

Hide file tree

Showing 147 changed files with 233 additions and 233 deletions.
diff --git a/files/en-us/glossary/base64/index.html b/files/en-us/glossary/base64/index.html
@@ -25,7 +25,7 @@
  <li><code><a href="/en-US/docs/Web/API/WindowOrWorkerGlobalScope/atob">atob()</a></code>: decodes a base64 encoded string("atob" should be read as "ASCII to binary").</li>
 </ul>
 
-<p>The algorithm used by <code>atob()</code> and <code>btoa()</code> is specified in <a href="https://tools.ietf.org/html/rfc4648">RFC 4648</a>, section 4.</p>
+<p>The algorithm used by <code>atob()</code> and <code>btoa()</code> is specified in <a href="https://datatracker.ietf.org/doc/html/rfc4648">RFC 4648</a>, section 4.</p>
 
 <p>Note that <code>btoa()</code> expects to be passed binary data, and will throw an exception if the given string contains any characters whose UTF-16 representation occupies more than one byte. For more details, see the documentation for <code><a href="/en-US/docs/Web/API/WindowOrWorkerGlobalScope/btoa">btoa()</a></code>.</p>
 

diff --git a/files/en-us/glossary/cacheable/index.html b/files/en-us/glossary/cacheable/index.html
@@ -46,7 +46,7 @@
 <ol>
  <li>General knowledge
   <ol>
-   <li>Definition of <a href="https://tools.ietf.org/html/rfc7231#section-4.2.3">cacheable</a> in the HTTP specification.</li>
+   <li>Definition of <a href="https://datatracker.ietf.org/doc/html/rfc7231#section-4.2.3">cacheable</a> in the HTTP specification.</li>
   </ol>
  </li>
  <li>Technical knowledge

diff --git a/files/en-us/glossary/caldav/index.html b/files/en-us/glossary/caldav/index.html
@@ -19,6 +19,6 @@ <h3 id="General_Knowledge">General knowledge</h3>
 <h3 id="Technical_reference">Technical reference</h3>
 
 <ul>
- <li><a href="https://tools.ietf.org/html/rfc4791">RFC 4791: Calendaring extensions to WebDAV (CalDAV)</a></li>
- <li><a href="https://tools.ietf.org/html/rfc6638">RFC 6638: Scheduling Extensions to CalDAV</a></li>
+ <li><a href="https://datatracker.ietf.org/doc/html/rfc4791">RFC 4791: Calendaring extensions to WebDAV (CalDAV)</a></li>
+ <li><a href="https://datatracker.ietf.org/doc/html/rfc6638">RFC 6638: Scheduling Extensions to CalDAV</a></li>
 </ul>
diff --git a/files/en-us/glossary/carddav/index.html b/files/en-us/glossary/carddav/index.html
@@ -19,5 +19,5 @@ <h3 id="General_knowledge">General knowledge</h3>
 <h3 id="Technical_reference">Technical reference</h3>
 
 <ul>
- <li><a href="https://tools.ietf.org/html/rfc6352">RFC 6352: vCard Extensions to Web Distributed Authoring and Versioning (WebDAV)</a></li>
+ <li><a href="https://datatracker.ietf.org/doc/html/rfc6352">RFC 6352: vCard Extensions to Web Distributed Authoring and Versioning (WebDAV)</a></li>
 </ul>
diff --git a/files/en-us/glossary/client_hints/index.html b/files/en-us/glossary/client_hints/index.html
@@ -10,7 +10,7 @@
 ---
 <p><span class="seoSummary"><strong>Client Hints</strong> are a set of <a href="/en-US/docs/Web/HTTP/Headers">HTTP request header</a> fields for proactive content negotiation allowing clients to indicate a list of device and agent specific preferences.</span></p>
 
-<p>Use of client hints isn't automatic: rather, servers must announce that they support client hints. Servers announce support for Client Hints using the <code><a href="https://tools.ietf.org/html/draft-grigorik-http-client-hints-03#section-2.2.1">Accept-CH</a></code> (accept client hints) header or an equivalent HTML meta element with the <code><a href="/en-US/docs/Web/HTML/Element/meta#attributes">http-equiv</a></code> attribute.</p>
+<p>Use of client hints isn't automatic: rather, servers must announce that they support client hints. Servers announce support for Client Hints using the <code><a href="https://datatracker.ietf.org/doc/html/draft-grigorik-http-client-hints-03#section-2.2.1">Accept-CH</a></code> (accept client hints) header or an equivalent HTML meta element with the <code><a href="/en-US/docs/Web/HTML/Element/meta#attributes">http-equiv</a></code> attribute.</p>
 
 <p><code>Accept-CH: Width, Viewport-Width, Downlink</code></p>
 

diff --git a/files/en-us/glossary/dtls/index.html b/files/en-us/glossary/dtls/index.html
@@ -21,7 +21,7 @@ <h3 id="Specifications">Specifications</h3>
 
 <ul>
  <li>{{RFC(6347, "Datagram Transport Layer Security Version 1.2")}}</li>
- <li><a href="https://tools.ietf.org/html/draft-ietf-tls-dtls13">Datagram Transport Layer Security Protocol Version 1.3 <em>draft specification</em></a></li>
+ <li><a href="https://datatracker.ietf.org/doc/html/draft-ietf-tls-dtls13">Datagram Transport Layer Security Protocol Version 1.3 <em>draft specification</em></a></li>
 </ul>
 
 <h3 id="Related_specifications">Related specifications</h3>

diff --git a/files/en-us/glossary/entity_header/index.html b/files/en-us/glossary/entity_header/index.html
@@ -6,7 +6,7 @@
   - WebMechanics
 ---
 <div class="notecard note">
-<p>The current HTTP/1.1 specification no longer refers to entities, entity headers or entity-body. Some of the fields are now referred to as representation header fields (<a href="https://tools.ietf.org/html/rfc7231#section-3" rel="noopener">RFC 7231, section 3: Representations</a>).</p>
+<p>The current HTTP/1.1 specification no longer refers to entities, entity headers or entity-body. Some of the fields are now referred to as representation header fields (<a href="https://datatracker.ietf.org/doc/html/rfc7231#section-3" rel="noopener">RFC 7231, section 3: Representations</a>).</p>
 </div>
 
 <p>An entity header is an {{glossary("header", "HTTP header")}} that describes the payload of an HTTP message (i.e. metadata about the message body). Entity headers include: {{HTTPHeader("Content-Length")}}, {{HTTPHeader("Content-Language")}}, {{HTTPHeader("Content-Encoding")}}, {{HTTPHeader("Content-Type")}}, {{HTTPHeader("Expires")}}, etc. Entity headers may be present in both HTTP request and response messages.</p>

diff --git a/files/en-us/glossary/hpkp/index.html b/files/en-us/glossary/hpkp/index.html
@@ -12,6 +12,6 @@ <h2 id="Learn_more">Learn more</h2>
 <ul>
  <li>{{HTTPHeader("Public-Key-Pins")}}</li>
  <li>{{HTTPHeader("Public-Key-Pins-Report-Only")}}</li>
- <li><a href="https://tools.ietf.org/html/rfc7469">RFC 7469 </a></li>
+ <li><a href="https://datatracker.ietf.org/doc/html/rfc7469">RFC 7469 </a></li>
  <li>Wikipedia: <a href="https://en.wikipedia.org/wiki/HTTP_Public_Key_Pinning">HTTP Public Key Pinning</a></li>
 </ul>
diff --git a/files/en-us/glossary/http_header/index.html b/files/en-us/glossary/http_header/index.html
@@ -58,7 +58,7 @@
 <ol>
  <li>Specifications
   <ol>
-   <li>Syntax of <a href="https://tools.ietf.org/html/rfc7230#section-3.2">headers</a> in the HTTP specification.</li>
+   <li>Syntax of <a href="https://datatracker.ietf.org/doc/html/rfc7230#section-3.2">headers</a> in the HTTP specification.</li>
   </ol>
  </li>
  <li>Technical Reference

diff --git a/files/en-us/glossary/idempotent/index.html b/files/en-us/glossary/idempotent/index.html
@@ -37,7 +37,7 @@ <h2 id="Learn_more">Learn more</h2>
 <h3 id="General_knowledge">General knowledge</h3>
 
 <ul>
- <li>Definition of <a href="https://tools.ietf.org/html/rfc7231#section-4.2.2">idempotent</a> in the HTTP specification.</li>
+ <li>Definition of <a href="https://datatracker.ietf.org/doc/html/rfc7231#section-4.2.2">idempotent</a> in the HTTP specification.</li>
 </ul>
 
 <h3 id="Technical_knowledge">Technical knowledge</h3>

diff --git a/files/en-us/glossary/nntp/index.html b/files/en-us/glossary/nntp/index.html
@@ -18,5 +18,5 @@ <h3 id="General_knowledge">General knowledge</h3>
 <h3 id="Technical_reference">Technical reference</h3>
 
 <ul>
- <li>From the IETF: <a href="https://tools.ietf.org/html/rfc3977">RFC 3977 about NNTP</a> (2006)</li>
+ <li>From the IETF: <a href="https://datatracker.ietf.org/doc/html/rfc3977">RFC 3977 about NNTP</a> (2006)</li>
 </ul>
diff --git a/files/en-us/glossary/payload_body/index.html b/files/en-us/glossary/payload_body/index.html
@@ -30,4 +30,4 @@
 \r\n
 </pre>
 
-<p>For more information see <a href="https://tools.ietf.org/html/rfc7230#section-3.3" rel="noopener">RFC 7230, section 3.3: Message Body</a> and <a href="https://tools.ietf.org/html/rfc7230#section-3.3.1" rel="noopener">RFC 7230, section 3.3.1: Transfer-Encoding</a>.</p>
+<p>For more information see <a href="https://datatracker.ietf.org/doc/html/rfc7230#section-3.3" rel="noopener">RFC 7230, section 3.3: Message Body</a> and <a href="https://datatracker.ietf.org/doc/html/rfc7230#section-3.3.1" rel="noopener">RFC 7230, section 3.3.1: Transfer-Encoding</a>.</p>
diff --git a/files/en-us/glossary/pop/index.html b/files/en-us/glossary/pop/index.html
@@ -13,9 +13,9 @@
 <section id="Quick_links">
 <ul>
  <li>{{Interwiki("wikipedia", "Post Office Protocol", "POP")}} on Wikipedia</li>
- <li><a href="https://tools.ietf.org/html/rfc1734">RFC 1734</a> (Specification of POP3 authentication mechanism)</li>
- <li><a href="https://tools.ietf.org/html/rfc1939">RFC 1939</a> (Specification of POP3)</li>
- <li><a href="https://tools.ietf.org/html/rfc2449">RFC 2449</a> (Specification of POP3 extension mechanism)</li>
+ <li><a href="https://datatracker.ietf.org/doc/html/rfc1734">RFC 1734</a> (Specification of POP3 authentication mechanism)</li>
+ <li><a href="https://datatracker.ietf.org/doc/html/rfc1939">RFC 1939</a> (Specification of POP3)</li>
+ <li><a href="https://datatracker.ietf.org/doc/html/rfc2449">RFC 2449</a> (Specification of POP3 extension mechanism)</li>
  <li><a href="/en-US/docs/Glossary">MDN Web Docs Glossary</a>:
   <ul>
    <li>{{Glossary("IMAP4")}}</li>

diff --git a/files/en-us/glossary/quic/index.html b/files/en-us/glossary/quic/index.html
@@ -28,7 +28,7 @@ <h3 id="Resources">Resources</h3>
 
 <ul>
  <li><a href="https://www.chromium.org/quic">Chromium Projects Documentation</a></li>
- <li><a href="https://tools.ietf.org/html/draft-tsvwg-quic-protocol-02">IETF Draft</a></li>
+ <li><a href="https://datatracker.ietf.org/doc/html/draft-tsvwg-quic-protocol-02">IETF Draft</a></li>
 </ul>
 
 <h2 id="See_also">See also</h2>

diff --git a/files/en-us/glossary/request_header/index.html b/files/en-us/glossary/request_header/index.html
@@ -33,5 +33,5 @@ <h3 id="Technical_knowledge">Technical knowledge</h3>
 
 <ul>
  <li><a href="/en-US/docs/Web/HTTP/Headers">List of all HTTP headers</a></li>
- <li><a href="https://tools.ietf.org/html/rfc7231#section-5" rel="noopener">RFC 7231, section 5: Request header fields</a></li>
+ <li><a href="https://datatracker.ietf.org/doc/html/rfc7231#section-5" rel="noopener">RFC 7231, section 5: Request header fields</a></li>
 </ul>
diff --git a/files/en-us/glossary/robots.txt/index.html b/files/en-us/glossary/robots.txt/index.html
@@ -16,6 +16,6 @@ <h3 id="General_knowledge">General knowledge</h3>
 <ul>
  <li>{{Interwiki("wikipedia", "Robots.txt")}} on Wikipedia</li>
  <li><a href="https://developers.google.com/search/reference/robots_txt" rel="nofollow">https://developers.google.com/search/reference/robots_txt</a></li>
- <li>Standard specification draft: <a href="https://tools.ietf.org/html/draft-rep-wg-topic-00">https://tools.ietf.org/html/draft-rep-wg-topic</a></li>
+ <li>Standard specification draft: <a href="https://datatracker.ietf.org/doc/html/draft-rep-wg-topic-00">https://datatracker.ietf.org/doc/html/draft-rep-wg-topic</a></li>
  <li><a href="https://www.robotstxt.org/" rel="nofollow">https://www.robotstxt.org/</a></li>
 </ul>
diff --git a/files/en-us/glossary/rtsp/index.html b/files/en-us/glossary/rtsp/index.html
@@ -15,7 +15,7 @@ <h3 id="General_knowledge">General knowledge</h3>
 
 <ul>
  <li>{{Interwiki("wikipedia", "Real_Time_Streaming_Protocol","RTSP")}} on Wikipedia</li>
- <li><a href="https://tools.ietf.org/html/rfc7826">RFC 7826</a> (one of the documents that specifies precisely how the protocol works)</li>
+ <li><a href="https://datatracker.ietf.org/doc/html/rfc7826">RFC 7826</a> (one of the documents that specifies precisely how the protocol works)</li>
 </ul>
 
 <section id="Quick_links">

diff --git a/files/en-us/glossary/safe/index.html b/files/en-us/glossary/safe/index.html
@@ -31,7 +31,7 @@ <h2 id="Learn_more">Learn more</h2>
 <h3 id="General_knowledge">General knowledge</h3>
 
 <ul>
- <li>Definition of <a href="https://tools.ietf.org/html/rfc7231#section-4.2.1">safe</a> in the HTTP specification.</li>
+ <li>Definition of <a href="https://datatracker.ietf.org/doc/html/rfc7231#section-4.2.1">safe</a> in the HTTP specification.</li>
 </ul>
 
 <h3 id="Technical_knowledge">Technical knowledge</h3>

diff --git a/files/en-us/glossary/stun/index.html b/files/en-us/glossary/stun/index.html
@@ -22,5 +22,5 @@ <h3 id="General_knowledge">General knowledge</h3>
 <h3 id="Technical_reference">Technical reference</h3>
 
 <ul>
- <li><a href="https://tools.ietf.org/html/rfc5389">Specification</a></li>
+ <li><a href="https://datatracker.ietf.org/doc/html/rfc5389">Specification</a></li>
 </ul>
diff --git a/files/en-us/glossary/tls/index.html b/files/en-us/glossary/tls/index.html
@@ -20,7 +20,7 @@
 <ol>
  <li>Specifications
   <ol>
-   <li><a href="https://tools.ietf.org/html/rfc5246" rel="external">RFC 5246</a> (The Transport Layer Security Protocol, Version 1.2)</li>
+   <li><a href="https://datatracker.ietf.org/doc/html/rfc5246" rel="external">RFC 5246</a> (The Transport Layer Security Protocol, Version 1.2)</li>
   </ol>
  </li>
  <li>Wikipedia articles

diff --git a/files/en-us/glossary/ttl/index.html b/files/en-us/glossary/ttl/index.html
@@ -36,9 +36,9 @@ <h3 id="Technical_reference">Technical reference</h3>
 
 <ul>
  <li>
-  <p><a href="https://tools.ietf.org/html/rfc2181#section-8">RFC 2181</a> on IETF</p>
+  <p><a href="https://datatracker.ietf.org/doc/html/rfc2181#section-8">RFC 2181</a> on IETF</p>
  </li>
  <li>
-  <p><a href="https://tools.ietf.org/html/rfc1035">RFC1035</a> on IETF</p>
+  <p><a href="https://datatracker.ietf.org/doc/html/rfc1035">RFC1035</a> on IETF</p>
  </li>
 </ul>
diff --git a/files/en-us/glossary/udp/index.html b/files/en-us/glossary/udp/index.html
@@ -23,5 +23,5 @@ <h3 id="General_knowledge">General knowledge</h3>
 <h3 id="Technical_reference">Technical reference</h3>
 
 <ul>
- <li><a href="https://tools.ietf.org/html/rfc768">Specification</a></li>
+ <li><a href="https://datatracker.ietf.org/doc/html/rfc768">Specification</a></li>
 </ul>
diff --git a/files/en-us/glossary/uri/index.html b/files/en-us/glossary/uri/index.html
@@ -16,5 +16,5 @@ <h3 id="General_knowledge">General knowledge</h3>
 
 <ul>
  <li>{{Interwiki("wikipedia", "URI")}} on Wikipedia</li>
- <li><a href="https://tools.ietf.org/html/rfc3986">RFC 3986 on URI</a></li>
+ <li><a href="https://datatracker.ietf.org/doc/html/rfc3986">RFC 3986 on URI</a></li>
 </ul>
diff --git a/files/en-us/learn/server-side/apache_configuration_htaccess/index.html b/files/en-us/learn/server-side/apache_configuration_htaccess/index.html
@@ -349,7 +349,7 @@ <h2 id="Frame_Options">Frame Options</h2>
 
 <p>The example below sends the <code>X-Frame-Options</code> response header with DENY as the value, informing browsers not to display the content of the web page in any frame to protect the website against <a href="https://www.owasp.org/index.php/Clickjacking">clickjacking</a>.</p>
 
-<p>This might not be the best setting for everyone. You should read about <a href="https://tools.ietf.org/html/rfc7034#section-2.1">the other two possible values for the <code>X-Frame-Options</code> header</a>: <code>SAMEORIGIN</code> and <code>ALLOW-FROM</code>.</p>
+<p>This might not be the best setting for everyone. You should read about <a href="https://datatracker.ietf.org/doc/html/rfc7034#section-2.1">the other two possible values for the <code>X-Frame-Options</code> header</a>: <code>SAMEORIGIN</code> and <code>ALLOW-FROM</code>.</p>
 
 <p>While you could send the <code>X-Frame-Options</code> header for all of your website's pages, this has the potential downside that it forbids even any framing of your content (e.g.: when users visit your website using a Google Image Search results page).</p>
 
@@ -385,7 +385,7 @@ <h2 id="Block_access_to_hidden_files_and_directories">Block access to hidden fil
 
 <p>In Macintosh and Linux systems, files that begin with a period are hidden from view but not from access if you know their name and location. These types of files usually contain user preferences or the preserved state of a utility, and can include rather private places like, for example, the <code>.git</code> or <code>.svn</code> directories.</p>
 
-<p>The <code>.well-known/</code> directory represents <a href="https://tools.ietf.org/html/rfc5785">the standard (RFC 5785)</a> path prefix for "well-known locations" (e.g.: <code>/.well-known/manifest.json</code>, <code>/.well-known/keybase.txt</code>), and therefore, access to its visible content should not be blocked.</p>
+<p>The <code>.well-known/</code> directory represents <a href="https://datatracker.ietf.org/doc/html/rfc5785">the standard (RFC 5785)</a> path prefix for "well-known locations" (e.g.: <code>/.well-known/manifest.json</code>, <code>/.well-known/keybase.txt</code>), and therefore, access to its visible content should not be blocked.</p>
 
 <pre class="brush: bash">&lt;IfModule mod_rewrite.c&gt;
     RewriteEngine On

diff --git a/files/en-us/mozilla/add-ons/webextensions/api/dns/resolve/index.html b/files/en-us/mozilla/add-ons/webextensions/api/dns/resolve/index.html
@@ -39,7 +39,7 @@ <h3 id="Parameters">Parameters</h3>
   <li><code>"canonical_name"</code>: The canonical name of the specified host will be queried.</li>
   <li><code>"disable_ipv4"</code>: Only IPv6 addresses will be returned.</li>
   <li><code>"disable_ipv6"</code>: Only IPv4 addresses will be returned.</li>
-  <li><code>"disable_trr"</code>: Do not use the Trusted Recursive Resolver (TRR) for resolving the host name. A TRR enables resolving of host names using a dedicated <a href="https://tools.ietf.org/html/draft-ietf-doh-dns-over-https-02">DNS-over-HTTPS</a> server.</li>
+  <li><code>"disable_trr"</code>: Do not use the Trusted Recursive Resolver (TRR) for resolving the host name. A TRR enables resolving of host names using a dedicated <a href="https://datatracker.ietf.org/doc/html/draft-ietf-doh-dns-over-https-02">DNS-over-HTTPS</a> server.</li>
   <li><code>"offline"</code>: Only literals and cached entries will be returned.</li>
   <li><code>"priority_low"</code>: The request is given lower priority. If "priority_medium" is also given, the query is given medium priority.</li>
   <li><code>"priority_medium"</code>: The request is given medium priority. If "priority_low" is also given, the query is given medium priority.</li>

diff --git a/files/en-us/mozilla/add-ons/webextensions/api/identity/index.html b/files/en-us/mozilla/add-ons/webextensions/api/identity/index.html
@@ -37,7 +37,7 @@ <h3 id="Getting_the_redirect_URL">Getting the redirect URL</h3>
 <p>You get the redirect URL by calling {{WebExtAPIRef("identity.getRedirectURL()")}}. This function derives a redirect URL from the add-on's ID.  To simplify testing, set your add-on's ID explicitly using the <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/browser_specific_settings">browser_specific_settings</a></code> key (otherwise, each time you <a href="https://extensionworkshop.com/documentation/develop/temporary-installation-in-firefox/">temporarily install the add-on</a>, you get a different redirect URL).</p>
 
 <p>{{WebExtAPIRef("identity.getRedirectURL()")}} returns a URL at a fixed domain name and a subdomain derived from the add-on's ID. Some OAuth servers (such as Google) only accept domains with a verified ownership as the redirect URL. As the dummy domain cannot be controlled by extension developers, the default domain cannot always be used.
-Loopback addresses are an accepted alternative that do not require domain validation (based on <a href="https://tools.ietf.org/html/rfc8252#section-7.3">RFC 8252, section 7.3</a>). Starting from Firefox 86, the following format is also permitted as a value for the redirect URL (see {{bug(1635344)}} for more details):
+Loopback addresses are an accepted alternative that do not require domain validation (based on <a href="https://datatracker.ietf.org/doc/html/rfc8252#section-7.3">RFC 8252, section 7.3</a>). Starting from Firefox 86, the following format is also permitted as a value for the redirect URL (see {{bug(1635344)}} for more details):
 <code>http://127.0.0.1/mozoauth2/[subdomain of URL returned by identity.getRedirectURL()]</code></p>
 
 <div class="notecard note">

diff --git a/files/en-us/mozilla/add-ons/webextensions/api/webrequest/certificateinfo/index.html b/files/en-us/mozilla/add-ons/webextensions/api/webrequest/certificateinfo/index.html
@@ -13,7 +13,7 @@
 ---
 <div>{{AddonSidebar()}}</div>
 
-<p>An object describing a single <a href="https://tools.ietf.org/html/rfc5280">X.509 certificate</a>.</p>
+<p>An object describing a single <a href="https://datatracker.ietf.org/doc/html/rfc5280">X.509 certificate</a>.</p>
 
 <p>The {{WebExtAPIRef("webRequest.SecurityInfo", "SecurityInfo")}} object returned from the {{WebExtAPIRef("webRequest.getSecurityInfo()")}} API includes a <code>certificates</code> property which is an array of these objects.</p>
 
@@ -43,7 +43,7 @@ <h2 id="Type">Type</h2>
  <dt><code>rawDER</code></dt>
  <dd><code>Array</code> of <code>Number</code>. If <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest/getSecurityInfo" title="Use this function to get detailed information about the TLS connection associated with a particular request."><code>webRequest.getSecurityInfo()</code></a> was called with the <code>rawDER</code> option present and set to <code>true</code>, this will contain the DER encoding of the certificate.</dd>
  <dt><code>serialNumber</code></dt>
- <dd><code>String</code>. The certificate's <a href="https://tools.ietf.org/html/rfc5280#section-4.1.2.2">serial number</a>.</dd>
+ <dd><code>String</code>. The certificate's <a href="https://datatracker.ietf.org/doc/html/rfc5280#section-4.1.2.2">serial number</a>.</dd>
  <dt><code>subject</code></dt>
  <dd><code>String</code>. Name of the organization that issued this certificate, represented as a Distinguished Name and formatted as a comma-separated list of Relative Distinguished Names, each of the form "type=value".</dd>
  <dd>For example: "<span class="message-body-wrapper"><span class="message-flex-body"><span class="devtools-monospace message-body"><span class="objectBox objectBox-string">CN=*.cdn.mozilla.net,O=Mozilla Corporation,L=Mountain View,ST=California,C=US</span></span></span></span>".</dd>
@@ -53,7 +53,7 @@ <h2 id="Type">Type</h2>
 
  <dl class="reference-values">
   <dt><code>sha256</code></dt>
-  <dd><code>String</code>. Base64 encoded SHA-256 hash of the DER-encoded <a href="https://tools.ietf.org/html/rfc5280#section-4.1.2.7">public key info</a>.</dd>
+  <dd><code>String</code>. Base64 encoded SHA-256 hash of the DER-encoded <a href="https://datatracker.ietf.org/doc/html/rfc5280#section-4.1.2.7">public key info</a>.</dd>
  </dl>
  </dd>
  <dt><code>validity</code></dt>