already responded

Justin Huff jjhuff at
Fri May 11 18:22:18 UTC 2007

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?


More information about the perlbal mailing list