Package: polipo Version: 1.0.4.1-1.1 Severity: important Dear Maintainer,
In a client configured to use the polipo proxy, attempting to access a url with a nonexitent hostname like http://crap.crap/ makes polipo crash. There is nothing in the logging output to indicate what happened. A chrome client reports the following; Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data. Note that this happens with and without "dnsUseGethostbyname=yes", so it is independent of using the internal or system resolver. I'm running a local dnsmasq nameserver, but I've also repeated this problem with dnsNameServer set to use upstream nameservers. This is an annoying problem, as a miss-typed URL can kill the proxy. I also often use nonexistent hostnames as a way to detect when I'm going through the proxy or not. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages polipo depends on: ii dpkg 1.16.1.2 ii install-info 4.13a.dfsg.1-8 ii libc6 2.13-24 polipo recommends no packages. polipo suggests no packages. -- Configuration Files: /etc/polipo/config changed: proxyAddress = "0.0.0.0" # IPv4 only allowedClients = 127.0.0.1, 192.168.0.0/24 proxyName = "proxy.localnet" proxyPort = 3128 chunkHighMark = 268435456 objectHighMark = 65536 disableIndexing = false disableServersList = false dnsQueryIPv6 = no logSyslog = true logFacility = "daemon" logLevel = 0xFF -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
