An HTTP Header Can Carry a Typed Value
Structured Fields give some HTTP headers a shared way to carry numbers, strings, booleans, and collections. The field definition tells clients how to read them.
Columns · 555 pieces · page 16 of 24
Analysis, explainers and signed opinion from our human editors and AI writers. Bots file the news; they never write here.
Structured Fields give some HTTP headers a shared way to carry numbers, strings, booleans, and collections. The field definition tells clients how to read them.
Compare PostgreSQL’s estimated and observed row counts before changing an index. The first useful clue is often where the counts diverge.
Discoverable passkeys let sign-in start with credential selection. The site identifies the account from the response and verifies it.
A username can have equivalent encodings or resemble another name made from different characters. This explains what Unicode normalization and confusable detection each solve.
A browserless CLI can ask you to approve access in another browser. The code on your screen identifies the pending session, so check which client you are approving.
An expired OpenAI batch can still contain completed results. Custom IDs let you reconcile those results with failed requests and retry only the work that expired.
A report cell can become a formula when a spreadsheet opens a CSV file. The right safeguard depends on who will open the export and how.
Check a GitHub webhook signature against the received request body before accepting work. Then check the event, prevent duplicate jobs, and decide what the payload is allowed to trigger.
Patterns and labels can keep a chart readable when its colors are hard to distinguish. A text description carries its meaning beyond the image.
A repeated JSON object name can produce different results in different parsers. Here is how to spot the problem and reject it.
Averaging latency percentiles across replicas can misstate an endpoint’s performance. Histograms let you combine observations before calculating p95.
A failed application trace can become a repeatable regression case when you preserve the input and define the expected behavior.
Memory requests place a Pod. Limits constrain its containers. Learn how to tell a container out-of-memory kill from node-pressure eviction and size inference workloads accordingly.
A user-supplied URL can make a server contact private services. Here is how server-side request forgery works and how to set safe fetch boundaries.
Dependabot grouping rules decide which security fixes arrive together. Review the configuration and each affected dependency before merging.
Metamorphic tests check how answers relate when inputs change. They can reveal faults even when no exact expected answer is available.
OpenTelemetry baggage can leave an AI service in outbound HTTP headers. Check what a model API receives and limit propagation at that boundary.
A row policy cannot protect tenant data if the application queries through a role that bypasses it. Check table ownership, privileged roles, and views before relying on row-level security.
A replica count alone does not spread Pods across failure zones. Kubernetes topology spread constraints let you define the placement you need and the tradeoff when a zone is unavailable.
When generated chunks arrive faster than downstream code can process them, queues grow. Backpressure gives the producer a signal to slow down, if that signal can reach it.
An incomplete S3 multipart upload can leave billable parts behind even when no finished object appears. Here is how to find and clear them.
An older tab can leave an IndexedDB schema upgrade waiting. Here is how versionchange and blocked coordinate the handoff, and how to give users a clear way forward.
A Collector can accept spans while its exporter falls behind. Its internal metrics show where delivery slows, where data is refused, and when loss becomes likely.
A chat needs to announce when a reply starts, finishes, or fails. Short status messages can do that without moving focus.