Web Explained
A 206 Response Can Be a Successful Request for Part of a File
Partial Content sounds like a download has gone wrong, but HTTP status 206 can mean the server successfully supplied the specific portion the client…
Everyday technology, a little clearer
Web Explained
Plain-language explanations for the web’s less obvious behaviour.
Web Explained
A Collapsed Details Box Can Contain Text Already in the Page
Understand a basic HTML disclosure box and distinguish expanding existing content from assuming a button must fetch a new page.
Web Explained
A 304 Response Can Mean Your Cached Copy Is Still Usable
Read HTTP 304 as part of a conditional request rather than assuming that every response without a new page body is a failed download.
Web Explained
A 429 Response Asks You to Check Request Limits
Understand HTTP 429 as a rate-limiting response and look for retry guidance instead of repeatedly refreshing a service that is already limiting requests.
Web Explained
A HEAD Request Checks Headers Without Downloading the Response Body
Distinguish HTTP HEAD from GET when reading a diagnostic result, and avoid treating a successful header check as a full page rendering test.
Web Explained
A 401 and a 403 Point to Different Access Problems
Understand the intended difference between HTTP 401 and 403, then collect the right details before asking a site owner for help with access.
Web Explained
Reader View Simplifies a Page, So Check the Original When Context Matters
Browser Reader View can make an article easier to read, but it changes the presentation. Return to the original page for surrounding controls, captions or information you cannot find.
Web Explained
Find on This Page Does Not Search the Whole Website
Browser Find is useful for locating words on the current page. Learn when to use it, when to switch to site search, and what a no-match result can actually tell you.