Re: issue with pipelining

Hi Juliusz,

    I have attached a tcpdump trace and a snapshot of where i saw Polipo
closing the connection without waiting for the response.
In the highlighted packets you would see, that it pipelines two requests,
and only waits for response for one and then sends out a Fin to close the
connection.

Varun

On Sat, May 23, 2009 at 3:09 PM, Juliusz Chroboczek <
[email protected]> wrote:

> >   I have come across a problem with pipelining. Polipo pipelines  two
> > requests to the HTTP1.1 server, and closes the connection after receiving
> > the response to first request.
>
> No, it doesn't.
>
> Polipo keeps track for each server whether it supports pipelining.
> Initially, a server is ``unknown'', and Polipo doesn't pipeline to it.
> After a while, Polipo will send two requests to the server to probe it
> for pipelining.  If pipelining doesn't work within 20 seconds, Polipo
> drops the connection and doesn't use pipelining with this server.
>
> So what you're seeing is either a buggy server, or a case where Polipo
> wrongly determined that the server is buggy.  I'll need a protocol trace
> to find out which.
>
>                                        Juliusz
>

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com

_______________________________________________
Polipo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/polipo-users