Summary: | Akregator cannot load http urls through proxy | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | Manuel Siggen <manuel> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | manuel |
Priority: | NOR | ||
Version: | 4.7.2 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Manuel Siggen
2011-10-26 11:25:48 UTC
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 *** |