Re: Firefox+polipo occasionally stop communicating

"Oliver Muth" <[email protected]> wrote:

> Fabian Keil wrote:
> > "Oliver Muth" <[email protected]> wrote:
> >> Now how can I avoid this? Who is to blame? How can I find out more?
> >
> > You could try checking with netstat to see if there are any
> > connections open between polipo and Firefox.
> 
> netstat -taep revealed that one of polipo's sockets was staying in CLOSE_WAIT status forever:
> 
> tcp 1 0 localhost:8123 localhost:55010 CLOSE_WAIT proxy 333512 2093/polipo

Was this the the only connection?

Even if it really originated from Firefox, I wouldn't expect it
to matter for Firefox's internal accounting anymore.

> Now this is a bit over my head, so please bear with me.
> Does this mean firefox has not properly requested or acknowledged closing of the port (and it is firefox' fault), or has firefox closed the port but polipo for whatever reason has not done so(and it is polipo's fault)?

Without a packet dump it's hard to tell.

BTW, another thing you could test is if a "hanging" Firefox
still opens direct connection to site for which you added
a proxy exception and if that works even if the request
is made to Polipo's proxy port.

Fabian

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)

iEYEARECAAYFAk8HKegACgkQBYqIVf93VJ2Q+QCcDYl/EsDATbF9zSlMnMSiG0gP
xfgAoJFosW10lEMY0eH7pEe080bA4Qvh
=SHVk
-----END PGP SIGNATURE-----