IHDR ` Ö S&À sRGB ®Îé gAMA ±üa pHYs t tÞfx ÿ¥IDAT Loooking inside the the PNG file, I notice that it has prepended HTML tags to the actual binary PNG content: ĮTag: "3a526f8ec280c24b946da13106f4afcc2eb61a0b" "PROPFIND /seafdav/ HTTP/1.1" 200 7693 "-" "Cyberduck/5.6 (Windows 8.1/6.3) (x86)"Īlso, seafdav.log has no contents and no other logs from the seafile /logs folder shows any entry related to the time that Cyberduck attempted connecting.Īlso, if I leave the Cyberduck option " Preferences > Transfers > General > Transfer files = Open multiple connections" (which is the default) and I download a PNG file then the contents of the downloaded file are corrupt. The apache logs don’t show any peculiarity when Cyberduck gave that error after login: - "HEAD /seafdav/ HTTP/1.1" 200 3290 "-" "Cyberduck/5.6 (Windows 8.1/6.3) (x86)" If I click “Try again” then it instantly shows the directory with the Libraries. Upon opening the connection Cyberduck shows “Login successful” in the status bar but then pauses for about 10 seconds and fails with a popup saying “Not a valid DAV response (200 OK), Try again?”.
#Cyberduck slow password
I configured Cyberduck for Webdav HTTP/SSL, port 443, hostname, added /seafdav to More options > path name and used the correct username and password when prompted. What referer? This doesn’t look right… Using Cyberduck There is an error in seahub_django_request.log: 16:17:39,291 django.request:98 _reject Forbidden (Referer checking failed - no Referer.): / The only line in the apache log is: - "OPTIONS /seafdav HTTP/1.1" 401 4137 "-" "Microsoft-WebDAV-MiniRedir/" The apache access log shows a 401 response, which means Auth failed (but it never prompted me). This fails instantly saying “The folder you chose does not appear to be valid.
#Cyberduck slow windows 8.1
I then tried the Windows 8.1 圆4 native client by opening a connection to htttps:///seafdav. Sadly, it’s much slower than using the browser or Cyberduck to upload and download (about 3 times slower for some reason …). Listed the tree, was able to download files (contents were fine) and also upload files. I tried to verify that seafdav works by navigating using Chrome to htttps:///seafdav and I could login fine and see the libraries, and also downloaded a file, checking that its contents are correct. Webdav via Seafdav however is only working via BitKinex but sadly this is slower than all other Webdav clients. The web gui and Seafile OS sync client are working just fine.
I’m using Ubuntu 16.04.1 with Apache 2.4 with the Community Edition 6.0.7 under Apache SSL, with a valid SSL certificate.
0 kommentar(er)
