Bug 408315 - Dolphins prepends "http://" when using "fish://" or "sftp://" in the location bar with a defined path
Summary: Dolphins prepends "http://" when using "fish://" or "sftp://" in the location...
Status: CONFIRMED
Alias: None
Product: dolphin
Classification: Applications
Component: general (other bugs)
Version First Reported In: 20.08.2
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-04 20:06 UTC by Ignacio Taranto
Modified: 2020-10-29 09:43 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ignacio Taranto 2019-06-04 20:06:33 UTC
SUMMARY
Dolphins prepends "http://" when using "fish://" or "sftp://" in the location bar.

STEPS TO REPRODUCE
1. Type fish://root@xxx.xxxx.xxx.xxx:~ in the location bar and press Enter

OBSERVED RESULT
Dolphin resolves to the location: http://fish/root@10.218.72.83:~/ and opens
the previous address in a web browser.

EXPECTED RESULT
Dolphin does not modify the typed address and displays the working dir of the SSH session.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.12.8
KDE Frameworks Version: 5.55.0
Qt Version: 5.9.7

ADDITIONAL INFORMATION
OS: openSUSE Leap 15.1
Comment 1 Ignacio Taranto 2019-06-04 20:09:11 UTC
The observed result is http://fish/root@xxx.xxx.xxx.xxx:~/
Comment 2 Julian Steinmann 2019-06-05 05:50:30 UTC
I can confirm this, but at least for me the problem only happens if I supply a path to be opened. If I simply enter 'fish://user@server.com', the connection is established correctly.

SYSTEM INFO
Operating System: KDE neon 5.15
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.58.0
Qt Version: 5.12.0
Comment 3 Ignacio Taranto 2019-06-05 13:27:50 UTC
Yes, it only happens when you supply a path.
Comment 4 Justin Zobel 2020-10-29 09:43:24 UTC
I can confirm this issue but only when using the ~

If you use a full path it's fine.

So the issue is with using the ~ character. It needs to replace the ~ with /home/$USERNAME