Each scenario opens a response whose body streams or stalls. The proxy peeks
response bodies before forwarding; a peek that waits for a byte cap or EOF on a
stream that provides neither holds the headers until a timeout. PASS
means tungsten answered with a success status; an error status or a dead wire is
a FAIL. The timing columns are diagnostic: a 200 whose first byte arrives at
stream end means the response was store-and-forwarded (inspected as a file), not
streamed. Fetch/XHR requests classify as
resource kind — for download-classification scenarios use the
navigation links or curl instead.
| Scenario | URL | Headers | First byte | Bytes (3m cap) | Result |
|---|
Expected failures:
scenarios that hold the response open (“then hold” rows, and the unbounded
navigation repros below) have no EOF. If policy classifies one as a download and routes
it to file-server, file-server buffers waiting for an EOF that never comes, times out,
and aborts — the row shows FAIL [502] or KILLED. That is a
file-server capability gap (it inspects only complete files), not a tungsten transport
bug. Exempting the site from download classification (PE application list) makes the row
pass.