Bug 220113

Summary: Akregator fails to fetch feed with empty password
Product: [Applications] akregator Reporter: Shai <shai>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: 1.5.3   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Shai 2009-12-26 01:18:02 UTC
Version:           1.5.3 (using 4.3.4 (KDE 4.3.4), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.32-trunk-686

This bug was first filed in Debian as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562241. Quoting myself from there:

My company uses services from 37Signals -- Basecamp
and Highrise. Highrise has an Atom feed of our latest
activity. Lately, 37Signals changed the authentication
mechanisms; instead of my user and password, I should
now use an "API Token" as user with an empty password
to authenticate.

Trying to fetch the feed URL this way in a browser
works. Using the API Token as username with an empty
password for fetching the feed in Thunderbird works.
I could read the feed perfectly well until this week,
and I have no reason to suspect any change in the
feed itself -- just the authentication.

In Akregator, I get "fetch error".

Thanks,
	Shai.
Comment 1 Shai 2009-12-26 01:24:53 UTC
I pressed "submit" too fast...

I forgot to mention: I successfully reproduced the bug on KDE and Akregator built from clean sources (trunk of a couple of weeks ago); hence the posting here.
Comment 2 Denis Kurz 2016-09-24 19:40:19 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 21:50:38 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.