In article <e6443ee5.0502180053.71e4fa52@posting.google.com >,
suyog.upadhye@wipro.com (suyog) wrote:

> Barry Margolin <barmar@alum.mit.edu> wrote in message
> news:<barmar-7CEB03.08193817022005@comcast.dca.giganews.com>...
> > Each request and response is independent. Every response has to be
> > fully formed, with a response code line, response-headers, and an
> > optional body. Persistent connections just save the client from having
> > to reconnect -- everything else is the same.
>
> Thanks for the suggestion.

What suggestion?

> The first request is served properly but on subsequent request it is
> failing, I have traced the problem and have found that there will be
> some more data remaining on the socket after the first request which
> causes failure for the 2nd request

More data on which socket? If it's on the server's socket, it sounds
like you're not putting the correct Content-Length: header in a POST or
PUT request. If it's on the client, it isn't reading the entire
response properly.

--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***