Bugzilla – Bug 859520
privoxy,yast proxy settings,error
Last modified: 2014-07-11 14:46:25 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 opensuse 13.1 , kde 4.12.1 privoxy 3.0.21-2.4.1 i use yast proxy manager to set system proxy settings then i click on "test" then yast manager says "error reported by privoxy unknown error code" then i click on "ok" to quit test then i click on "ok" to quit proxy manager then proxy manager says proxy settings are well set . i experiment with browsers then no pb . all is ok what is this error ? ****************************************************************************** * Rebuilt URL to: http://www.novell.com/ * Adding handle: conn: 0x251aaf0 * Adding handle: send: 0 * Adding handle: recv: 0 * Curl_addHandleToPipeline: length: 1 * - Conn 0 (0x251aaf0) send_pipe: 1, recv_pipe: 0 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* About to connect() to proxy localhost port 8118 (#0) * Trying ::1... * Connexion refusée * Trying 127.0.0.1... * Connected to localhost (127.0.0.1) port 8118 (#0) > GET http://www.novell.com/ HTTP/1.1 > User-Agent: curl/7.32.0 > Host: www.novell.com > Accept: */* > Proxy-Connection: Keep-Alive > < HTTP/1.1 301 Moved Permanently < Date: Mon, 20 Jan 2014 15:09:18 GMT * Server Apache is not blacklisted < Server: Apache < Location: http://www.novell.com/home/ < Content-Length: 319 < Age: 66 < X-Mag: 7CFDEB6C02633A18;911bf594;67625209;usrLkup->0;usrBase->0;getPRBefFind->0;getPRBefFind->0;PRAfterFind->0;www_root;publicURL->0;FP4->0; < Via: 1.1 www.novell.com (Access Gateway-ag-7CFDEB6C02633A18-67625209) < Keep-Alive: timeout=300, max=81 < Connection: Keep-Alive < Content-Type: text/html; charset=iso-8859-1 < Set-Cookie: lb_novell=NNODEBIJ; Domain=.novell.com; Path=/ < Proxy-Connection: keep-alive < 0 319 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0{ [data not shown] 100 319 100 319 0 0 776 0 --:--:-- --:--:-- --:--:-- 776 * Connection #0 to host localhost left intact ****************************************************************************** Reproducible: Always Steps to Reproduce: 1. 2. 3.
It is a problem with parsing the proxy reply in the test. *** This bug has been marked as a duplicate of bug 853725 ***