I'm writing a load test client, and want to make sure I handle pipelined requests right. I installed Red Hat 8.0 and its Apache 2.0, and made an html file that referenced all the .gif's in /icons. Fetching that page with Mozilla, I do indeed observe pipelined requests and responses.
I have seen pipelined requests in which a particular HTTP request header line starts in one TCP segment and ends in another, but I have not yet seen the same thing for HTTP response lines from Apache. Does Apache 2.0 do anything special to prevent that (presumably to avoid triggering bugs in clients that assume that HTTP response lines aren't split across successive read()'s)? Thanks, Dan
