> I'm trying to use Polipo to cache connections to reduce overhead in an
> application which is doing RPC via HTTP POSTs.
>
> I've got it to use the proxy, but I still only see one request per
> connection (despite the fact that it's keeping persistent connections
> open).
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.
This is not a problem for idempotent requests (GET and HEAD), which
Polipo will resend automatically if the server shuts down the
connection at the wrong time. Obviously, you don't want POST requests
to be resent automatically, especially if they're asking to debit your
bank account.
The solution is to use a reliable protocol, not HTTP, for RPC.
> Is there an option which controls this?
No. This is a feature, not a bug.
If you really wish to hack around that (which I do not recommend),
check the code around line 912 in httpServerSideRequest .
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
