Bug 118247 - No proxy support in akregator for KDE 3.5
Summary: No proxy support in akregator for KDE 3.5
Status: RESOLVED FIXED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 1.2
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 120087 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-12-13 16:32 UTC by Mats Söderlind
Modified: 2009-11-27 22:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mats Söderlind 2005-12-13 16:32:46 UTC
Version:           1.2 (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

After upgrading to KDE 3.5 akregator no longer fetch any feeds outside our corporate proxy.  Other readers are able to fetch feeds as well as konqueror can fetch both feeds and other Web-pages.
Comment 1 Frank Osterfeld 2006-01-22 21:38:02 UTC
I just tested following proxy setup:

I use "manually specify proxy settings" with localhost:4715 as proxy, and a list of domains which should be routed over that proxy. 
4715 is forwarded via ssh to the www proxy at my university.

I added slashdot.org to the domain list before trying to fetch the slashdot feed.

a) When the ssh tunnel is down, fetching in Akregator fails as expected.
b) When the tunnel is up, it works.

So Akregator seems to respect the proxy settings you can specify in KControl/Konqueror.

I use current SVN (~3.5.1) and Eike reported a) for 3.5.0.
Can you test the localhost:4715 scenario (testing a), without having a ssh tunnel)? So we know whether your proxy settings are ignored completely, or if the Akregator<->Proxy communication fails for some reason.
Comment 2 Mats Söderlind 2006-01-25 10:33:44 UTC
OK, I'm also using manually specified proxy settings.  In my case all traffic 
is routed via the proxy with the exception of local domains.  The only feed 
that can be fetched is a local feed.

When I use KNewsTicker all feeds can be fetched so there is no blocking done 
in the proxy.

Regards,

On Sunday 22 January 2006 21:38, Frank Osterfeld wrote:
[bugs.kde.org quoted mail]
Comment 3 Frank Osterfeld 2006-01-25 23:41:52 UTC
*** Bug 120087 has been marked as a duplicate of this bug. ***
Comment 4 Leon Bottou 2006-05-22 23:10:50 UTC
I experienced that problem and found that our
firewall system blocks http requests with
an user agent containing the words "gator"
(which they say is a well known spyware).

Akregator-1.2.2 queries the servers using 
the user agent string "Akregator/1.2.2; librss-remnants"
which is not configurable.  Bad idea..

Workaround: use khexedit to locate the 
string "Akregator/" and patch it as "Akregatar/".  
Then everything works as it should.




Comment 5 Falco Hirschenberger 2006-08-08 13:23:06 UTC
I have another strange effect with tunneled Rss feeds. I subscribed a https feed which was tunneled through a firewall. It was tunneled lake that:

   ssh -L 6666:TARGET_HOST:443 TO_BE_TUNNELED_HOST

I can read the feed and get new messages on updates, but if I enable the option to display the website directly, it fails with the message:

https://localhost:6666:6666/PATH_TO_RSS_FEED

For some strange reason the port number was doubled in the URL akregator wants to open. This is definitely a bug.

I don't know if I should open a new bug for this.
Comment 6 Raúl 2009-11-19 13:08:56 UTC
Hello:

This is an old bug and it works for me on akregator 4.3.1. Could anyone confirm as well so this bug can be closed?

Thanks.
Comment 7 Christophe Marin 2009-11-27 22:38:03 UTC
(In reply to comment #6)
> Hello:
> 
> This is an old bug and it works for me on akregator 4.3.1. Could anyone confirm
> as well so this bug can be closed?
> 
> Thanks.

Yep, works as expected in KDE > 4.3. (tested with privoxy turned off, akregator is then unable to fetch feeds.)