I've just discovered than :
without limit connect, the error is "port 5222 is not authorized"
with the limit-connect, the error is "writing error"
So it seems like the "limit-connect" is well understood and that the
problem happens somewhere else (and I have no idea why).
** Changed in: privoxy (Ubuntu)
Status: New => Invalid
--
limit-connect config doesn't have any effect
https://bugs.launchpad.net/bugs/307111
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
universe-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
