LLM Request Smuggling with Content-Length and Transfer-Encoding
LLM request smuggling begins when two HTTP recipients disagree about where one request ends and the next begins. Conflicting Content-Length and Transfer-Encoding fields are the classic fault line. In an AI gateway chain, the disagreement can place hidden bytes beyond the inspected prompt and ahead of the next authenticated request. This guide covers strict rejection, canonical reserialization, connection handling, protocol translation, and negative tests.