Bug 130529

Summary: support for rss on https protokol missing
Product: [Applications] akregator Reporter: Ferdinand Gassauer <gassauer>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: wishlist    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Ferdinand Gassauer 2006-07-09 20:34:41 UTC
Version:           1.2.3 (using KDE 3.5.3, compiled sources)
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release 2.6.16.13-4-default

Hi!
Akregator could use the wallet to access the sites with access control
Comment 1 Ferdinand Gassauer 2006-07-09 20:49:21 UTC
phpgedview readme says:

Passing any supported type including "PIE0.1", "mbox","RSS0.91", "RSS1.0", "RSS2.0",
"OPML", "ATOM0.3", "HTML", "JS" will change the feed type.

I can see the the feeds in konqueror if I enter
https://<myip>/ged/rss.php?rssStyle=RSS2.0
but akregator says 
Feed not found from https://<myip>/ged/rss.php?rssStyle=RSS2.0.
Comment 2 Frank Osterfeld 2006-07-10 00:57:05 UTC
As you are mentioning the wallet, are you sure you are talking about https as such, and not about http login? (which is reported in http://bugs.kde.org/show_bug.cgi?id=110419)
https works here with the one https feed I have around, though I am not sure about what happens when KHTML doesn't trust the certificate.
Comment 3 Thorsten Holtkaemper 2006-11-27 11:26:32 UTC
Using KDE 3.5.5 and 3.3.x https feeds work (SSL is used for authentication and for the feed). The root certificate for the server certificate is known to KDE. I didn't test with servers with self-signed certificates.
Comment 4 Thorsten Holtkaemper 2006-11-27 11:34:57 UTC
Addition to my comment #3: kwallet works for the authentication. Though when using the session management akregator crashes kded (100% load) and mangles somehow the kwalletmanager so that my wallet is not visible to any application afterwards (when restarting without akregator everthing is fine again).
Comment 5 John Scott 2019-04-07 02:17:10 UTC
This bug is old, and Akregator has supported HTTPS for a long time now.