ゆるテックノート

Documentation Index

About this site

These are casual notes to help you get the gist of my online tools. Not a formal spec—just takeaways and tips I’ve collected and rewritten in plain language. Read with a light touch.

Saml

Uuid

Unix

Hash

Data

Web

What is the World Wide Web?

Covers the difference between the Internet and the Web, how URLs are structured, how HTTP works, why HTTPS is now the default, and handy troubleshooting tips.

Why “www” showed up in front

“www” is just a subdomain. Here’s why it became a convention to mark web servers, the DNS/CDN reasons, cookie scoping, pros/cons, and how people choose today.

Organizations that keep the Web running

Quick tour of W3C and IETF for standards, ICANN/IANA and regional registries for names and numbers, and how browsers, cloud/CDN providers, and security groups keep the Web running.

DNS basics in one page

Quickly explains recursive/caching resolvers, authoritative servers, the query flow, and how DNSSEC signatures are validated.

What are DNS root servers?

DNS root servers sit at the top of the hierarchy, serving the root zone. There are 13 identifiers (A–M), each anycasted to many physical sites worldwide. This covers their role, the “13” misconception, and practical notes.

The long, layered browser UA string

Explains why UA strings pile up tokens like Mozilla/KHTML/Gecko/Chrome, the historical compatibility reasons, and today’s move to UA reduction and User-Agent Client Hints.

What is 418 I'm a teapot?

Covers the joke status 418 I'm a teapot from RFC2324 (HTCPCP), where it shows up, and why it should stay out of production.

HTTP beyond HTML (yes, always)

HTTP was designed from the start as a generic request/response transport. Today it routinely carries JSON APIs, binaries, streaming, and more. Here’s a relaxed tour of the history and best practices.

Using HTTP request methods

A quick reference for HTTP methods in RFC 9110 (GET/POST/PUT/PATCH/DELETE/HEAD/OPTIONS/TRACE): safety, idempotency, typical use, and design tips.

HTTP methods × status codes

RFC 9110-aligned pairings of GET/POST/PUT/PATCH/DELETE with common status codes (200/201/204/304/400/401/403/404/409/412/415/422/429/500/503).

Conditional requests with ETag

RFC 9110 guide to conditional requests with ETag (If-Match, If-None-Match, If-Modified-Since, etc.) and how to return 304/412/428.

Methods and caching

RFC 9110-aligned overview of how GET/HEAD/POST interact with caches. Covers Cache-Control, ETag, Vary, and when POST responses can be cached.

CORS preflight and OPTIONS

When browsers send CORS preflight, what headers they include, and how to respond with Access-Control-Allow-* correctly. Aligned with RFC 9110 and the Fetch Standard.

HTTP method anti-patterns

Common misuses of HTTP methods that conflict with RFC 9110 or cause operational issues: state-changing GET, POST-everything, non-idempotent DELETE, and more.

HTTP version history in short

A concise look at how HTTP evolved from 0.9 to 1.1, then HTTP/2 (from SPDY) and HTTP/3 (QUIC), and what changed at each step.