The HTTP QUERY method is now a standard
RFC 10008 standardizes QUERY, a safe and idempotent HTTP method with a request body. It is the clean way to send a large or private query.
Topic · 28 stories · page 1 of 2
28 stories tagged http on AI Tamer, newest first.
RFC 10008 standardizes QUERY, a safe and idempotent HTTP method with a request body. It is the clean way to send a large or private query.
Check HTTP status separately from network and request failures.
Reading a response consumes its body stream. Clone before the body is locked or disturbed when two consumers need it.
How a per-response nonce authorizes inline and external scripts, and how strict-dynamic lets a trusted script vouch for everything it loads.
How one response header tells a browser to erase its own cookies, cache, and storage for an origin when a session ends.
Why gzip and brotli belong to the representation itself, while chunked transfer is about how bytes cross the wire.
Why no-cache still allows caching and requires revalidation, while no-store forbids storing the response at all.
How the Strict-Transport-Security header turns one HTTPS visit into a standing rule to use only HTTPS for as long as max-age lasts.
How an informational 103 response pre-announces Link headers so a client can preload or preconnect while the server still works.
Browsers send an OPTIONS preflight for non-safelisted methods, headers or Content-Type values, the server answers with allow lists, and the browser alone decides whether the script sees the response.
How the WebSocket Upgrade handshake proves a server actually understands the protocol, and why client-to-server frames are XOR-masked even over TLS.
What the Content-Digest header actually protects against, and why a digest is not proof of origin without TLS or a signature.
How the Vary response header tells a cache which request fields a response depends on, and why Vary: * blocks reuse without revalidation.
How the If-Match header and strong entity tags implement optimistic locking, so a slower editor can't silently overwrite a faster one.
A network call can hang while connecting, while waiting for the next byte, or by dribbling data forever. Connect, read and total timeouts each cover one of those, and some clients set none by default.
stale-while-revalidate and stale-if-error permit different kinds of bounded staleness. Their windows start after freshness ends, and each trades current data for a specific benefit.
A POST followed by a redirect can become a GET or remain a POST. The choice between 303, 307, 308, and historic 301/302 behavior changes what a form or API client sends next.
A source crawler can ask whether a page has changed before downloading it again. HTTP conditional requests provide the signal.
A partial download is useful only when the remaining bytes belong to the same file. HTTP range requests and validators let you check before appending.
Use curl --fail-with-body when a script needs to detect an HTTP error and keep the response text that explains it.
HTTP 202 means a request was accepted while processing remains unfinished. An asynchronous AI job needs a place where people can learn its outcome.
A cached response can depend on request headers as well as the URL. `Vary` tells caches which headers to compare before reuse.
The part after # points into a retrieved resource. It is removed before an HTTP request, so changing it alone cannot select a different server response.
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.