Forum

hello,

recently i migrated my small personal webserver to hiawatha and it feels really good. so first of all i like to express my thanks for hiawatha.
Everythings works fine exept webdav access for owncloud and I have no idea how to fix it.

What i did so far:
Checked website and the interwebs but didnt find any information on my specific problem i understand. Consulted the owncloud mailingslist, on which i was told that missing serverside webdav support is no problem, since owncloud ships with a webdav implementation (exactly because of independence from webserver). On the owncloud website (owncloud.org) it is documented how to set up clients, i tested with a gentoo/KDE SC system via the dolphin filebrowser and a Windows 7 system, but the connection attempts only time out without any meaningful error codes. Then i checked the hiawatha access and error logfiles, but only the Windows connection was reckognized:
"ip.address|date:time|200|155||OPTIONS / HTTP/1.1|Connection: keep-alive|User-Agent: Microsoft-WebDAV-MiniRedir/6.1.7600|translate: f|Host: example.net"

Hiawatha version: 0.8.1
Operating System: Debian 6.0.4
Owncloud version: 3

I am happy to supply any needed information. Any pointers to what I could check, test or have to learn are very welcome.

thanks a lot

Hello Hugo,

du you have any suggestions what I could test / configure / read to understand the problem?

thanks a lot for your help.

Sorry for the late response, forgot this one.

I don't see how a web application can have WebDAV support since it is something a webserver should support. Can you tell me where I can find the ownCloud mailinglist discussion?

thank you very much for the reply.
you can find the discussion at: http://mail.kde.org/pipermail/owncloud/2012-March/002692.html

I've sent the ownCloud developer an e-mail to found it what ownCloud requires from a webserver. I like this ownCloud and really like to see it running on Hiawatha.

that sounds promising. thank you very much.
especially since there is an offline client available, I cant wait to include it in my productive setup.

It looks like I've got it all working. Download the beta of Hiawatha 8.2 here [www.leisink.org]. Compile and install as usual. This version has a new option for WebDAV applications like ownCloud.

VirtualHost {
  ...
  WebDAVapp = yes
}

Last step is a bugfix in the ownCloud code. Open 3rdparty/Sabre/HTTP/Response.php and change line 93 to

return header("Status: ".$this->getStatusMessage($code));

With this, I was able to open my files in ownCloud via WebDAV on my Mac laptop.

I've updated the 8.2 beta package. It has write and delete capabilities now. I've tested it with CyberDuck [cyberduck.ch].

testing in progress...
btw: the make_debian_package depends on a cmake version which is only available through squeeze-backports repo

You can download and install the latest version from cmake.org.

awesome!
With the updated beta i can access owncloud via Dolphin.

Need to test with Windows, the sync-client mirall and other device later.

some updates:
webdav and webdavs works with gnu/linux. Surprisingly also with Symbian v.9.3 S60 3rd Edition FP2 something which one could find on older Nokia Business phones like E72 (though webdavs is mandatory on these devices).
I couldnt get webdav working on Windows 7, however, there might be a chance i screwed that up myself (i somewhat errr... customized the installation).
Unfortunatly also the mirall offline snyc client doesnt work. Neither with Fedora nor Windows 7. It connects and can create sync-directories, but fails at syncing. At least on Fedora mirall complains about System Time of the machines involved differs to much. I have set both to the same time zone. (Beside, i was able to sync under Windows and with mirall on the Apache implementation.)

...stupid me: after restarting hiawatha, the system time error went away.

i encountered another problem with uploading files. i cant upload files bigger than 64kb neither webdav nor browser upload. i have checked the php.ini, but this is set to greater values. usually owncloud handles the upload file size via .htaccess.

Try the MaxRequestSize setting.

thanks, MaxRequestSize solved the upload issue (should check the documentation more often .

I did some more testing and indeed, the mirall client (http://owncloud.org/sync-clients) doesnt work on hiawatha. There are no entries in the hiawatha error log, but a few entries in the access.log.

Oke, will look into it.

I'm stunned to find a ownCloud / hiawatha Post on here :-) makes me really happy.
Hugo, i love the work you do with hiawatha! It's a great webserver.

rieper, could you please test if downloading files from your owncloud installation works?
I'm having trouble with this.

i uploaded a 80mb .zip file to my owncloud installation. that worked fine. but if i'm trying to download it via the download butten (say /download.php?files=file.zip), it stops after something between 9MB and 21MB. I tried several configurations for hiawatha and php-fcgi but nothing fixes the problem :-/

The donwload probably stops because it probably takes longer to download the file than the amount of runtime is given to the download.php script. Increase the value of TimeForCGI and try again.

No, doesn't work either. Funny thing is, this problem seens time independent. It doesn't matter if I'm on a 5Mbit/s or 50Mbit/s connection. It stops between 9 and 21MB every time.
I just noticed, I'm getting a lot of "aborted connection to db" errors from MariaDB (Mysql) in the syslog. seems the PHP Scripts are somehow killed, the download doesn't finish and the mysql connection is aborted.

An incorrect PHP setting perhaps?

Ah, Found it.
There was a TimeforCGI Directive in my vhost configs that was set to 15. That killed the PHP Download scripts every time.
Problem now is, a Download takes a certain time depending on how big the file and how fast the connection is. I don't want to kill the php script before it is finished. Any idea on how i can set it to allways wait to do it's job?
i tried

TimeForCGI = 60
WaitforCGI = yes
KillTimedoutCGI = no

but that didn't help.

Simply set TimeForCGI to a very high value:

TimeForCGI = 86400

ah i feared that would impact the performance to much. but heh, it's a big host.
Thank you very much for your help!
Again, i should allways look in all config files in case the vhost config overwrites the hiawatha.conf ;-) stupid me