Version: 2.1 (using KDE 3.1.3) Compiler: gcc version 2.95.4 20020320 [FreeBSD] OS: FreeBSD (i386) release 4.8-STABLE This seems to be the same both in kate and in konqueror. I can write a file over webdavs normally when the file is 4096 bytes or shorter but at 4097 bytes or more the save never finishes.
Could you please provide more information? 1) server details (ie. what software is in use) 2) whether this works with webdav:// 3) what happens to the upload - does it complete? 4) whether webdavs:// works on different servers 5) proxy details if applicable Thanks, Hamish.
1) Server is Zope with the ZServerSSL added for the SSL portions (ZServerSSL is available at http://www.post1.com/home/ngps/m2/) 2) I can upload the larger files normally over a regular webdav:// connection. I can also upload the larger files normally using the cadaver webdav client. (That actually uses a https:// url, but I am pretty sure it is the same as the webdavs:// connection) 3) When trying to upload the larger file, the file save dialog comes up, the progress bar goes to 100% and it just stops there. With shorter files, at that point the login dialog will come up (does not matter whether I have already given name/password for that file or that host already) and I can put in my name/password and the save completes. 4) Have not tried on other webdavs servers. 5) No proxy involved.
thanks... regarding 3, what happens to the copy of the file on the server? is it a complete copy of the file you are uploading (regardless of the fact the progress dialog doesn't disappear)?
The title of the dialog box shows "100% of 4.9kb (Moving)" and near the middle it says "foo.com contacted. Waiting for reply..." Often with the smaller files, at that point I will get the login dialog popup, but not in this case. If I cancel the upload dialog, the file on the server remains completely untouched. I had never tried letting the save "time out" before, but if the save is allowed to time out (after about 10 minutes) the file is actually saved to the server with all of the new changes complete.
Hi - is it possible for you to try this out with the latest beta of kde 3.2? Thanks... Hamish.
Tried this again on 3.2-beta1 and it still has the same problem.
I found another report of a webdavs client that has trouble with the zserverssl and zope. Here: http://www.zope.org/Members/glpb/dwhowto It describes a workaround (quite simple, and works for me :o) but I think this is still a bug in the kde code... Maybe the workaround will point you in the right direction to a cure (or maybe it's not a kde bug at all).
Are you referring to the tweak asking you to increase your buffers? ie. ac_in_buffer_size = 4096 -> 100000 ac_out_buffer_size = 4096 -> 100000 I have a feeling this is a SSL problem deeper in KDE than the webdav implementation... can someone else have a look? I'm a bit out of my depth here ;) Reassigning to kssl...
Yes. I made the changes to ac_in_buffer_size and ac_out_buffer_size and now I can save files larger than 4096 bytes. I assume the limit is the size of the buffer, but I have not tested it.
Do you still somehow think this is kssl related?
Can this be an issue of kssl not properly handling EAGAIN when doing writes? (Or be related somehow to the recently fixed EGAIN problem with reading...)
After adding George to CC: Can this be an issue of kssl not properly handling EAGAIN when doing writes? (Or be related somehow to the recently fixed EGAIN problem with reading...)
On Tuesday 10 August 2004 15:44, Waldo Bastian wrote: > After adding George to CC: > Can this be an issue of kssl not properly handling EAGAIN when doing > writes? (Or be related somehow to the recently fixed EGAIN problem with > reading...) Might be.. Not sure. Will need to investigate, but I likely can't do this before september now.
This bug is still present in KDE 3.3.2 and Kate 2.3.2 The Zope file that needs to be modified is different now. It used to be lib/python/ZServer/medusa/asynchat.py now it is lib/python/ZServer/medusa/http_server.py
How about KDE 3.4? I use webdavs regularly with large and small files.
In KDE 4.x secure connection is handled by Qt's network classes and since KDE 3.x is no longer maintained, closing this as unmaintained. If the problem still persists in KDE 4.x, feel free to reopen this ticket.