Description: When setting up a remote service with WebDAV, if the user keeps the leading "https://" in the host URL, the service will fail to connect as it only saves "https" as the host. Steps to Reproduce: 1. File > Open Remote... 2. Manage services > Add service 3. Fill in details for a WebDAV connection, keeping the "https://" at the beginning of the URL for the "Host" field (and using "Secure connection" for this example) 4. Click "OK": it fails to connect 5. Click "Manage services > Edit service" Actual Results: The settings: - use "https" as the host - use the port 80 even if "secure connection" was used - have prepended "//<host.url>/:443/" to the root value Expected Results: Host URLs are supported regardless of if they have the leading "https://" or not. Reproducible: Always User Profile Reset: Yes Additional Info: To connect to my NextCloud, I use the following settings: - Type: WebDAV - Host: nextcloud.instance.url (no HTTP(S) at the beginning) - Secure connection ticked (which changes the port to 443) - Label: label of your choice - Root: remote.php/dav/files/USERNAME/ Earliest version tested: Version: 7.0.6.2 Build ID: 00(Build:2) CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Ubuntu package version: 1:7.0.6-0ubuntu0.18.04.1_lo1 Calc: threaded But issue still present in: Version: 7.3.0.2 / LibreOffice Community Build ID: f1c9017ac60ecca268da7b1cf147b10e244b9b21 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
Created attachment 177805 [details] resulting erroneous WebDAV settings
*** Bug 148610 has been marked as a duplicate of this bug. ***
Confirming because of duplicate.
Dear Stéphane Guillou (stragu), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug