>> Polipo will always use a fresh connection for a POST or PUT request;
>> this is to avoid a race condition that is intrinsic in the HTTP protocol.
>> An HTTP server is allowed to shut down a persistent connection at any
>> time. This means in particular that it may shut down the connection
>> between the time a request is sent and the time it is received.
> A HTTP server is "allowed" to shut down whatever connection at any time.
> So _that_ is a bad reason to use virgin connections for POST.
Typical HTTP servers use a larger timeout after connection open than
for an idle connection. Additionally, they will shut down connections
after a given number of requests have been serviced.
Polipo tries really hard to only perform POSTs on connections that
have just been opened -- a connection that is opened, then remains
idle for a few seconds is *not* considered as frash. This makes the
likelihood of the race condition triggering extremely low.
> What does polipo do if it sees a connection close after a POST on a
> virgin connection??
It returns a 502 error to the client. It's then up to the client to
decide whether to retry the request.
Juliusz
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Polipo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/polipo-users
