Philip Martin <philip.mar...@wandisco.com> writes: > I can't reproduce this against a standard server.
I think I have worked it out. There was an error in my script: one of the XML response lines was missing a '\n' and this originally caused the client to report the HTTP response as too short, so I "fixed" it by added a trailing '\n'. When creating the next response in the script I copied the trailing '\n' but I didn't omit the earlier '\n'. The result is an HTTP response that is one byte too long. The dummy server was first sending 'Content-Length: 425' and then sending 426 bytes. This spurious extra byte causes serf to crash when it reads the extra data without a proper handler in place. What we need is an exact trace of every byte sent by your proxy to the client so we can check whether it is also sending an extra byte. -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*
