Version: 4.7.2 (using KDE 4.7.2) OS: Linux It seems Akregator does not use correctly the proxy settings configured in KDE. The main consequence is that external URLs are not loaded (the feed icon turns red and the feed is not updated). I experienced the same problem with Rekonq which then says : ERROR The requested URL could not be retrieved While trying to retrieve the URL: / The following error was encountered: Invalid URL Some aspect of the requested URL is incorrect. Possible problems: Missing or incorrect access protocol (should be `http://'' or similar) Missing hostname Illegal double-escape in the URL-Path Illegal character in hostname; underscores are not allowed Your cache administrator is cct.help@vd.ch. Generated Wed, 26 Oct 2011 11:20:55 GMT by proxy1.vd.ch (squid/2.5.STABLE3) I also tried with Chrome 15 (which uses the KDE proxy settings), but it works fine there. It worked fine with Akregator v1.6.6 (KDE 4.6.5). I tried the following configurations : 1) proxy configuration with URL : $ cat .kde/share/config/kioslaverc DoNotTrack=false PersistentProxyConnection=true [$Version] update_info=kioslave.upd:kde2.2/r1,kioslave.upd:kde2.2/r2,kioslave.upd:kde2.2/r3 [Proxy Settings] AuthMode=0 NoProxyFor= Proxy Config Script=http://proxy.vd.ch/proxy-conf/internet.pac ProxyType=2 ReversedException=false ftpProxy= httpProxy= httpsProxy= => Akregator/Rekonq : exernal URLs are *not* loaded, but local ones are. Chrome 15 : both external and local URLs are loaded. 2) manual proxy configuration (with checkbox 'use proxy only for entries in this list' unchecked) : $ cat .kde/share/config/kioslaverc DoNotTrack=false PersistentProxyConnection=true [$Version] update_info=kioslave.upd:kde2.2/r1,kioslave.upd:kde2.2/r2,kioslave.upd:kde2.2/r3 [Proxy Settings] AuthMode=0 NoProxyFor=etat-de-vaud.ch,vd.ch,localhost Proxy Config Script=http://proxy.vd.ch/proxy-conf/internet.pac ProxyType=1 ReversedException=false ftpProxy=http://proxy.vd.ch:8080 httpProxy=http://proxy.vd.ch:8080 httpsProxy=http://proxy.vd.ch:8080 => Akregator/Rekonq : exernal URLs are loaded, but local ones are *not*. Chrome 15 : exernal URLs are loaded, but local ones are *not*. 3) manual proxy configuration (with checkbox 'use proxy only for entries in this list' checked) : $ cat .kde/share/config/kioslaverc DoNotTrack=false PersistentProxyConnection=true [$Version] update_info=kioslave.upd:kde2.2/r1,kioslave.upd:kde2.2/r2,kioslave.upd:kde2.2/r3 [Proxy Settings] AuthMode=0 NoProxyFor=etat-de-vaud.ch,vd.ch,localhost Proxy Config Script= ProxyType=1 ReversedException=true ftpProxy=http://proxy.vd.ch:8080 httpProxy=http://proxy.vd.ch:8080 httpsProxy=http://proxy.vd.ch:8080 => Akregator/Rekonq : exernal URLs are *not* loaded, but local ones are. Chrome 15 : exernal URLs are *not* loaded, but local ones are. I restarted Akregator after each settings change. Finally, it seems that https URLs work fine with Rekonq with configuration #1 (but not http ones). I couldn't find any https feeds to check this behavior with Akregator. Reproducible: Always Steps to Reproduce: 1) configure a http proxy in KDE System Settings 2) start Akregator 3) try to refresh or add a feed (for instance http://lwn.net/headlines/newrss) Actual Results: The feed's icon turns red after a couple of secondes, and the feed isn't refreshed. Expected Results: The feed is refreshed and new items show up. OS: Linux (i686) release 3.0.0-12-generic-pae Compiler: gcc
I investigated a bit further and with the configuration #1 (proxy config through URL), I got the following traces (sudo ngrep -c 200 -d any port 8080) when trying to load www.google.com : Rekonq : T 10.247.161.133:41019 -> 145.232.254.21:8080 [AP] GET / HTTP/1.1..Host: www.google.com..Connection: keep-alive..User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.34 (KHTML, like Gecko) rekonq Safari/534.34..Accept: text/html,application/ xhtml+xml,application/xml;q=0.9,*/*;q=0.8..Accept-Encoding: gzip, deflate, x-gzip, x-deflate..Accept-Charset: utf-8,*;q=0.5..Accept-Language: ch, en_US..Cookie: NID=52=XTeK4HbVJYXAIDQKHRppJ2Fb6il mRgt2ma_1IOQacGO9_IJkglbuhZ3vk2jmaJM_WgD21vDtjEKM0Ol3spzR_A_g5HQieDl8d2YmCozoe8fmBx3chcwSjxXwnb2Q2Gk5; PREF=ID=00b5576a2147616c:U=7b2e81d7aa6cb461:FF=0:TM=1319619492:LM=1319620224:S=F5Z0q5UI6vvqe Kuu.... Chrome: T 10.247.161.133:40916 -> 145.232.254.21:8080 [AP] GET http://www.google.com/ HTTP/1.1..Host: www.google.com..Proxy-Connection: keep-alive..User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.102 Safari /535.2..Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8..Accept-Encoding: gzip,deflate,sdch..Accept-Language: en-US,en;q=0.8..Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0. 3..Cookie: NID=52=F1k2qSG1HZi4TrlkE1b1uZHwdPTjM5rA_00pPpbCPO9-8MByUN_Zsqjuo-_5jMY6HfAwLej6p9-0luSEdVEQXT8XeSeim-SQpMx_ZOCC_llqy7chJ-COJCpr0Xo5Eha3; PREF=ID=4bb0187bdd5a829e:U=89ad3d3d2ef01515:FF= 0:LD=en:CR=2:TM=1319620655:LM=1319620655:S=DZl82CKrpNwrFl0Q.... 145.232.254.21 is the proxy IP address, so the request *is* going through the proxy. The obvious difference is the param immediately following GET : Rekonq asks for / while Chrome asks for http://www.google.com/. I am not a proxy expert, so I cannot tell if it could a problem or not.
After a bit more digging, I found this bug to be a duplicate of bug 283794. *** This bug has been marked as a duplicate of bug 283794 ***