Version: (using KDE KDE 3.3.91) Installed from: SuSE RPMs OS: Linux Since 3.4 beta1 I cannot overwrite folders using webdav anymore. I am told that the folder already exists. Fair enough, yet maybe I want to overwrite it!? Expected behaviour would be to ask whether I want to overwrite the folder. If the folder to be overwritten has a sub-folder, ask again for the sub-folder. If I chose not to overwrite the folder but it has sub-folders, ask for each subfolder, if I want to overwrite it.
I haven't changed anything in the webdav code. If this worked before, it is either a konqueror or kio regression. If it didn't work before, it is a konqueror or kio feature request.
I also get an error when overwriting files in webdav. the (german) message is: Der Server war entweder nicht in der Lage, die angeführten Eigenschaften des XML-Elements "propertybehavior" zu gewährleisten oder Sie haben versucht, eine Datei zu überschreiben, obwohl Sie ein solches Überschreiben zuvor für unzulässig erklärt hatten. Anderenfalls wäre die Anforderung erfolgreich abgeschlossen worden. rough translation: "server was unable to provide the given properties of XML element "propertybehavior" or you tried to overwrite a file though you disallowed such overwriting before. otherwise, the request would have been finished properly." don't know it's just a server issue (mediacenter.gmx.net) and whether it worked before.
just found out that overwriting a file from inside kspread works very fine. it therefore must be a konqueror bug.
oops... my last two comments were about every kind of files. this is what happens for me with folders: - creating a new one with the name of an existing one produces a 'folder already exists' message --- should ask for another name - renaming an existing one to X while X is used as another folder's name produces the message posted in comment #2 --- should do what the reporter requests
This is an Konqueror issue. (I'm using Konqueror 3.5.7) Konqueror is obeying the protocol perfectly AFAICT, but is simply not making an overwrite request. When making MOVE requests (for both files or directories) Konqueror is sending the request with the "Overwrite" header equal to "F". Which is means "do not overwrite". If the resource exists, the server will return the request with error code 412. (MOVE and the Overwrite header http://www.webdav.org/specs/rfc2518.html#rfc.section.8.9.3) Konqueror then just seems to display a standard message for the 412 error code. If this ever worked before, and nobody changed the code, then the server was not honoring the Overwrite header. MOVE return codes: http://www.webdav.org/specs/rfc2518.html#rfc.section.8.9.4 Konqueror should either: 1. first check if the target exists, if it does, ask the user, and then use "Overwrite: T". 2. upon getting a 412 on a MOVE request, ask the user if it should try with the overwrite flag set.
konqueror 4.0 RC 2 - but also 3.5.8 create a new webdav folder: An unexpected error (200) occurred while attempting to create the requested folder. copy to a webdav folder: the folder <hostname> (!!!!) does not exist. cadaver and nautilus work fine.
BTW I can read,delete and move files with konqueror 3.5.8
What is the status of this bug withe KDE SC 4.3.4 and KDE SC 4.4 beta1 ?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!