Bug 144106

Summary:	Wrong links are shown when URL contains encoded %c3%a6r characters
Product:	[Applications] akregator	Reporter:	Öyvind Saether <oyvinds>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	russ
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:

Description Öyvind Saether 2007-04-12 00:12:35 UTC

Version:            (using KDE KDE 3.5.6)
Installed from:    Gentoo Packages
Compiler:          gcc (GCC) 4.1.1 
OS:                Linux

Original link in a RSS feed like /2007/04/08/tur-i-ufyselig-v%c3%a6r/

is shown as /2007/04/11/overvÃ¦rsÃ¸k/ in Kakregator, so visiting the link as displayed will give a 404 at the site you're visiting. Encoded chars like %c3 within the URL should be kept intact, not transformed (Kakregator really shouldn't try to change the URL given in the RSS feed at all?)

Comment 1 Russ Tennant 2009-02-20 22:32:15 UTC

I've also run into this problem during development. It re-encodes the URL which causes issues accessing the URL.

For example,

URL as present in LINK tag:

http://dev-nutechpark.vipasuite.com/partial/content-type/application%2Fatom%2Bxml/news/FdxbQVIpg543,bx327,bx329,cb870?FeedType=atom_1_0

URL Akregator tries to use:

http://dev-nutechpark.vipasuite.com/partial/content-type/application%252Fatom%252Bxml/news/FdxbQVIpg543,bx327,bx329,cb870%3FFeedType=atom_1_0

Since there is no longer a query part to the URL because the question mark was escaped, the "Akregator" URL isn't valid.

Comment 2 Denis Kurz 2016-09-24 19:41:10 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 22:33:40 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.