Bug 81847

Summary:	Make the DolphinPart able to read security information about WebDav servers and show it in Konqueror
Product:	[Applications] dolphin	Reporter:	Jesper Krogh <jesper>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	adawit, adrian
Priority:	NOR
Version:	16.12.2
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Jesper Krogh 2004-05-19 07:13:51 UTC

Version:            (using KDE KDE 3.2.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Unlike https is it not possible to see the security information about server-certificate, etc. when using webdavs://

Comment 1 Hamish Rodda 2004-05-26 15:29:26 UTC

Sounds like there's a special case for "https" in konq which needs to have "webdavs" added to it...?

Comment 2 George Staikos 2005-03-20 23:45:57 UTC

Actually that dialog comes from KHTML, not Konqueror.  What you are asking for, I believe, is "security" support in filemanager view.

Comment 3 Frans Englich 2006-10-02 13:33:03 UTC

I can confirm this. There's so feedback(e.g, the yellow, closed lock in the status bar), when being connected to a Web DAV server via SSL. Well, I'm not fully sure I am, since there's no feedback.


Frans

Comment 4 Jaime Torres 2008-07-19 23:07:00 UTC

It shows the green shield in the address bar in konqueror 4.2 svn trunk 831729 visiting https://mydisk.se/demo (user: demo/demo)

Comment 5 Dawit Alemayehu 2012-01-07 18:12:06 UTC

This needs to be implemented in the Dolphin part now since it is the one that provides file management services. It needs to look at the "ssl_*" meta data sent by KIO and request the showing of the security button by the embedding application.

Comment 6 Adrián Chaves (Gallaecio) 2012-10-07 17:27:04 UTC

Shouldn’t this be considered a feature request (wishlist) for Dolphin?

Comment 7 Justin Zobel 2021-03-09 02:18:45 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.