: Chunked is HTTP/1.1 only, so that could be the problem. --wunder well ... yes and no.
the *request* ab sends are specified as http/1.0, and in that request it uses the (non-RFC complieant but generally accepted) http/1.0 style keep-alive headers. jetty parses the http/1.0 request fine, but is sending an http/1.1 response back that uses the chunked responses (i can't remembe if that's kosher according to the spec, but it's what seems to be happening) ab is then (evidently) happily parsing that http/1.1 response, chunking and all, but some where alone the way, something is not prserving the goal of using Keep-Alive. bottom line: it's a mess and this is why no one should be using http/1.0. you sure as hell shouldn't be trying to test the perforance of an app using http/1.0 connections, unless you actually expect to be using http/1.0 in your production code -- and if you are, then good luck to you, but i've got no help to offer you. -Hoss
