Bug Hunting Session
Bug 61569 - FILESAVE: WebDav Save doesn't work anymore
Summary: FILESAVE: WebDav Save doesn't work anymore
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA needsApacheTomcat
Keywords:
: 67082 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-02-27 19:21 UTC by Marcio Lima
Modified: 2016-04-24 18:44 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcio Lima 2013-02-27 19:21:18 UTC
Problem description: The product does not save any document to webfolder using webdav. We note this issue using Apache WebDavServer (org.apache.catalina.servlets.WebdavServlet.). We do not try with other webdav server.
This is a huge problem since there are a lot of Tomcat container world wide expecting to receive files using webdav

This functionality aways works fine with OpenOffice until version 3.2.1

Steps to reproduce:
1. Save As -> http://[host]/myWebApp/myWebDAVMapping/myFile.odt
2. use any tomcat cantainer to receive the file
3. 

Current behavior: Apache webdav servlet receive a request to save from libreoffice and return a response and libreoffice can't understand the answer

Expected behavior: 

              
Operating System: All
Version: unspecified
Comment 1 tommy27 2013-08-26 14:54:41 UTC
what about Bug 67082. is it the same issue?
Comment 2 tommy27 2013-09-11 17:45:32 UTC
*** Bug 67082 has been marked as a duplicate of this bug. ***
Comment 3 CIS 2013-11-03 09:52:59 UTC
LibreOffice (V 4.0:build-305 OpenSuse Build) seems to be able to:

1. Open all corresponding Filetypes directly from a webdav- ressource
2. Save modifications on files, already existing on the webdav ressource, by using the same filenames. So files can be modified directly.

LibreOffice (V 4.0:build-305 OpenSuse Build) seems NOT to be able to:
1. Create new Files on a Webdav Ressource

Error Message1:
Fehler beim Speichern des Dokumentes Unbenannt1:
https://XXXXXXX/Unbenannt%201 existiert nicht.

Error Message2:
Fehler beim Speichern des Dokumentes Unbenannt1:
Allgemeiner Fehler.
Allgemeiner Ein-/Ausgabefehler.
--
Tested with Opensuse 12.3 (x64,KDE 4.10.5), LibreOffice 4.0:build-305 OpenSuse Build, Webdav Ressource by Egroupware V 1.8.004

Kind Regards
Comment 4 Robinson Tryon (qubit) 2013-11-24 21:54:18 UTC
NoRepro on LO Version: 4.2.0.0.beta1 on Ubuntu 12.04.3

(In reply to comment #0)
> 
> This functionality aways works fine with OpenOffice until version 3.2.1

Marking as regression

> Steps to reproduce:
> 1. Save As -> http://[host]/myWebApp/myWebDAVMapping/myFile.odt
> 2. use any tomcat cantainer to receive the file
> 3. 

I tested against our ownCloud server.
https://owncloud.documentfoundation.org/remote.php/webdav

I was able to open and save ODT files via LibreOffice (following these instructions: https://help.libreoffice.org/Common/Opening_a_Document_Using_WebDAV_over_HTTPS)

> Current behavior: Apache webdav servlet receive a request to save from
> libreoffice and return a response and libreoffice can't understand the answer

Ok. Looks like this might be specific to the Apache Tomcat server.
Whiteboard: NeedsApacheTomcat
Comment 5 tommy27 2014-11-03 19:43:11 UTC
can you retest with LibO 4.3.3.2?
Comment 6 Robinson Tryon (qubit) 2014-11-22 21:56:55 UTC
Relevant information from OO forums:
https://forum.openoffice.org/en/forum/viewtopic.php?f=83&t=60041

Looks like Tomcat is sending back a message w/ a "<multistatus xmlns="DAV:">" element in it. The good news is that "<status>HTTP/1.1 200 OK</status>", but perhaps we're not parsing that message correctly.
Comment 7 Robinson Tryon (qubit) 2015-02-03 15:28:49 UTC
(In reply to CIS from comment #3)
> LibreOffice (V 4.0:build-305 OpenSuse Build) seems NOT to be able to:
> 1. Create new Files on a Webdav Ressource

Sounds like our last confirming result was from 2013, with v4.0.

CIS/Marcio: Please test with a modern 4.4 or 4.5 build of LibreOffice and see if the problem remains.

Status -> NEEDINFO

(If the problem is still there, please change status back to UNCONFIRMED. Thanks)
Comment 8 QA Administrators 2015-09-04 02:55:43 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-09-03
Comment 9 QA Administrators 2015-10-14 19:48:40 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO

Message generated on: 2015-10-14
Comment 10 Jean-Baptiste Faure 2016-04-24 18:44:20 UTC
Was never set to NEW -> regression keyword removed.