While testing perlbal we ran into these messages: already responded. already responded [2]. They start immediately after perlbal has parsed the headers -- before a backend connection is created. They seem to happen occasionally on a POST that's preceded by a GET. If I get persist_client to off, the problem goes away. Any ideas? Thanks! --Justin