We found 6 results for "http" keyword
Agent instructions - why they drift from the project and how to catch it
You write the rules file for your AI once, and the agent works from it for months - including the months after half the rules stop being true. In the METR study from early 2025, experienced developers using AI were 19% slower, while feeling 20% faster. In this post I show how I solved it for myself. The instructions came under the same scrutiny as code, they got a gate of their own, and the gate got a test that checks it.
How an answer types itself out word by word: streaming over HTTP
An AI answer appears gradually not because of a visual effect but because of streaming: an HTTP response body is a stream, so the server can send it in chunks and the browser can show each one right away. On the front end you read it two ways - the dead-simple EventSource (SSE) or the flexible fetch with a stream - and it's the second one that the LLM libraries use under the hood.
Where cache lives: how many copies of one response exist at once
The same server response can sit in several caches at once - app memory, the Service Worker, the HTTP cache, the CDN - and the whole page is held by bfcache on top of that. Each has a different owner and something different clears it, so "clear cache" hits one of them, sometimes none. What's left is the question every such debugging session starts with: which layer is holding the stale copy, and what invalidates it.
HTTP caching: why the second visit to a site is instant
Take a single style.css file and follow its day on a live site: first the browser downloads it, then it serves it from memory without asking the server, then it asks the server whether its copy is still current and usually gets just a confirmation instead of the whole file, and after you deploy a new version it downloads it again. That one story is all of HTTP caching - Cache-Control, ETag, 304, and stale-while-revalidate.
Same-origin policy and CORS: who can read data from another server
The browser's same-origin policy (SOP) blocks JavaScript on one page from reading data from another domain - unless the server explicitly allows it through CORS. This post walks through how that server-side permission mechanism works, why you sometimes see a preflight OPTIONS request, and why you sometimes don't.
Hoisting in JavaScript - what the metaphor really means
The textbook explanation says declarations 'move to the top' of the code. The ECMA-262 spec doesn't define hoisting as a mechanism at all, and let behaves as if the rule didn't apply to it. So what really happens before your code runs, and why does the TDZ look exactly the way it does?
