/explore
|
You are here 
|
www.potaroo.net | ||
| | | | |
sookocheff.com
|
|
| | | | | Note: To make this easier to read (and write), h1 may be used in place of HTTP/1, and h2 may used in place of HTTP/2. HTTP/1 has a long and storied history. Originally developed as a sixty page specification documented in RFC 1945, it was designed to handle text-based pages that leverage hypermedia to connect documents to each other. Typical web pages would kilobytes of data. For example, the first web page was a simple text file with web links to other text documents. Now, the web is made up of media-rich sites containing images, scripts, stylesheets, fonts, and more. The size of a typical web page is measured in megabytes rather than kilobytes, and the number of requests required to assemble a full page can be over one hundred. The reality of how web pages... | |
| | | | |
educatedguesswork.org
|
|
| | | | | [AI summary] The text provides an in-depth analysis of encrypted DNS protocols (DoX) and their implications for security, privacy, and network management. Key points include the importance of secure channels for DNS queries, the role of DNSSEC in complementing DoX, and the challenges of implementing encrypted DNS in various network environments. The discussion covers different transport protocols like DoH and DoT, the use of DDR for resolver discovery, and the trade-offs between privacy and network control. The text also touches on the technical and policy aspects of encrypted DNS, including the need for trust in resolvers and the limitations of current implementations. | |
| | | | |
scorpil.com
|
|
| | | | | Short history of HTTP protocol | |
| | | | |
blog.thenewoil.org
|
|
| | | Password managers are thankfully becoming a mainstream topic. In addition to seeing commercials for certain ones from time to time, it's ... | ||
