zishuo/nip
1
0
Fork 0
mirror of https://github.com/cunnie/sslip.io.git synced 2025-10-31 02:46:35 +08:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Placate https://validator.w3.org

Browse Source 
fixes:
```
The name attribute is obsolete. Consider putting an id attribute on the nearest container instead.
```
This commit is contained in:
Brian Cunnie
2018-03-01 17:49:18 -08:00
parent 2961708fa7
commit 3c50a3181a
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
document_root/index.html
View File

@@ -156,12 +156,12 @@ src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> <![endif]-->
"https://drive.google.com/open?id=0ByweFu4TspftMWJPdE1US0hQTGc">here</a>.</p>
<hr>
<h4 id="footnotes">Footnotes</h4>
<p><a name="status" id="status"><sup>[Status]</sup></a> A status of “build failing” rarely means the system is
<p><a id="status"><sup>[Status]</sup></a> A status of “build failing” rarely means the system is
failing. It’s more often an indication that when the servers were last checked (currently every six hours), the
CI (continuous integration) <a href="https://ci.nono.io/teams/main/pipelines/sslip.io">server</a> had difficulty
reaching one of the four sslip.io nameservers. That’s normal. <sup><a href="#timeout" class=
"alert-link">[connection timed out]</a></sup></p>
<p><a name="timeout" id="timeout"><sup>[connection timed out]</sup></a></p>
<p><a id="timeout"><sup>[connection timed out]</sup></a></p>
<p>DNS runs over <a href="https://en.wikipedia.org/wiki/User_Datagram_Protocol">UDP</a> which has no guaranteed
delivery, and it’s not uncommon for the packets to get lost in transmission. DNS clients are programmed to
seamlessly query a different server when that happens. That’s why DNS, by fiat, requires at least two nameservers