Hi,

I'm using polipo as intermediate proxy for Firefox and some external proxy.

FF -- polipo -- external proxy

The local polipo should only act as replacement for the FF disk cache.
So I wonder what the best settings for Firefox communicating with polipo are 
when it comes to number of connections and pipelining.
Is it even possible to use polipo as SOCKS v5 proxy and does it have any 
advantage over http? It does not work however, the external proxy is http 
only.

My current polipo settings are:

,----[/etc/polipo/config]
| allowedClients = 127.0.0.1
| cacheIsShared = false
| censorReferer = maybe
| censoredHeaders = from, accept-language
| chunkHighMark = 104857600
| disableIndexing = false
| disableServersList = false
| diskCacheRoot = "/var/cache/polipo/"
| diskCacheTruncateTime = 9d12h
| logSyslog = true
| maxAge = 56d1h
| maxConnectionAge = 5h
| maxConnectionRequests = 10000
| maxExpiresAge = 100d1h
| objectHashTableSize = 0
| objectHighMark = 16384
| parentProxy = "proxy:8080"
| proxyAddress = "127.0.0.1"
| proxyName = "localhost"
| relaxTransparency = maybe
| serverIdleTimeout = 15m
| serverMaxSlots = 10
| serverSlots = 10
`----

So having 10 connections to the external proxy, does it make sense to have 
the equal number from the browser to polipo? Pipelining is enabled for both, 
I guess it only makes sense if both connections of polipo, to the browser 
and to the parentProxy, are pipelined?
Are websocket connections affected by polipo?

I'm unsure especially about
  max-persistent-connections-per-server
  pipelining.maxrequests
  pipelining.aggressive

My current Firefox-25.0.1 configuration...
I *marked* non-default settings:

,----[about:config network.http.*connect*]
| network.http.connection-retry-timeout;250
| network.http.connection-timeout;90
| *network.http.max-connections;10*
| *network.http.max-connections-per-server;10*
| *network.http.max-persistent-connections-per-proxy;10*
| *network.http.max-persistent-connections-per-server;10*
`----

,----[about:config network.http.pipelining]
| *network.http.pipelining;true*
| network.http.pipelining.abtest;false
| network.http.pipelining.aggressive;false
| network.http.pipelining.max-optimistic-requests;4
| network.http.pipelining.maxrequests;32
| network.http.pipelining.maxsize;300000
| network.http.pipelining.read-timeout;30000
| network.http.pipelining.reschedule-on-timeout;true
| network.http.pipelining.reschedule-timeout;1500
| *network.http.pipelining.ssl;true*
`----

,----[about:config network.websocket]
| network.websocket.allowInsecureFromHTTPS;false
| network.websocket.auto-follow-http-redirects;false
| network.websocket.delay-failed-reconnects;true
| network.websocket.enabled;true
| network.websocket.extensions.stream-deflate;false
| network.websocket.max-connections;200
| network.websocket.max-message-size;2147483647
| network.websocket.timeout.close;20
| network.websocket.timeout.open;20
| network.websocket.timeout.ping.request;0
| network.websocket.timeout.ping.response;10
`----

Best regards,
Massimo


------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing 
conversations that shape the rapidly evolving mobile landscape. Sign up now. 
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
Polipo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/polipo-users

Reply via email to