HTTP 403 in all webdav (seafdav) Android clients for PUT method
230 views
Skip to first unread message
Sergei Kuzmin
Sep 23, 2015, 8:01:53 AM9/23/15
to seafile
Hi everyone!
seafdav.log is empty. Other logs contain no useful info. Only if I switch to i.e. nginix I get some info in access.log
It is clear there so Cyberduck uploaded file successfully, but the same failed in Andoid. This makes impossible to use apps like FolderSync to overcome lack of Seafile sync on Android.
I have set a seafile server v4.3.2 with webdav extension according to http://manual.seafile.com/extension/webdav.html on a linux server. Everything works fine from Windows (Cyberduck), Linux (davfs). But I am unable to upload any file in any Android client as the server responds HTTP 403 Forbidden no matter which account, folder or client I use.
seafdav.conf:
[WEBDAV]
enabled = trueport = 9080fastcgi = falseshare_name = /seafdav.log is empty. Other logs contain no useful info. Only if I switch to i.e. nginix I get some info in access.log
192.168.1.5 - user@email [23/Sep/2015:14:40:32 +0300] "HEAD /seafdav/ HTTP/1.1" 200 0 "-" "Cyberduck/4.7.2.18004 (Windows 7/6.1) (x86)"192.168.1.5 - user@email [23/Sep/2015:14:40:33 +0300] "PROPFIND /seafdav/Documents/tmp/ HTTP/1.1" 207 1489 "-" "Cyberduck/4.7.2.18004 (Windows 7/6.1) (x86)"192.168.1.5 - user@email [23/Sep/2015:14:40:34 +0300] "PUT /seafdav/Documents/tmp/540x960.jpg HTTP/1.1" 201 401 "-" "Cyberduck/4.7.2.18004 (Windows 7/6.1) (x86)"192.168.1.5 - user@email [23/Sep/2015:14:40:35 +0300] "PROPFIND /seafdav/Documents/tmp/ HTTP/1.1" 207 2256 "-" "Cyberduck/4.7.2.18004 (Windows 7/6.1) (x86)"95.79.195.129 - user@email [23/Sep/2015:14:46:57 +0300] "PROPFIND /seafdav/Documents/tmp/ HTTP/1.1" 207 2256 "-" "ezdavplugin/2.08TotalCommander/2.62 (Android; en_EN)"95.79.195.129 - user@email [23/Sep/2015:14:46:59 +0300] "PUT /seafdav/Documents/tmp/540x960.jpg HTTP/1.1" 403 448 "-" "ezdavplugin/2.08 TotalCommander/2.62 (Android; en_EN)"95.79.195.129 - user@email [23/Sep/2015:14:47:02 +0300] "PROPFIND /seafdav/Documents/tmp/ HTTP/1.1" 207 2256 "-" "ezdavplugin/2.08TotalCommander/2.62 (Android; en_EN)"It is clear there so Cyberduck uploaded file successfully, but the same failed in Andoid. This makes impossible to use apps like FolderSync to overcome lack of Seafile sync on Android.
Is there any recommended Android client? Is there any logging configuration to find out the real problem?
Nicolas Sebrecht
Sep 25, 2015, 7:47:04 PM9/25/15
to sea...@googlegroups.com, Nicolas Sebrecht
On Wed, Sep 23, 2015 at 05:01:53AM -0700, Sergei Kuzmin wrote:
> Hi everyone!
> I have set a seafile server v4.3.2 with webdav extension according
> to http://manual.seafile.com/extension/webdav.html on a linux server.
> Hi everyone!
> I have set a seafile server v4.3.2 with webdav extension according
> Everything works fine from Windows (Cyberduck), Linux (davfs). But I am
> unable to upload any file in any Android client as the server responds
> HTTP 403 Forbidden no matter which account, folder or client I use.
> seafdav.conf:
Sounds like a bug to me. Report it... Well, I don't know where since
> unable to upload any file in any Android client as the server responds
> HTTP 403 Forbidden no matter which account, folder or client I use.
> seafdav.conf:
the team ignores messages here.
--
Nicolas Sebrecht
Sergei Kuzmin
Jan 11, 2016, 7:34:52 AM1/11/16
to seafile
UPDATE: The problem disappeared when I rooted my Android device. Although the webdav client does not require root permissions nor asks for them no syncronization errors occurs anymore.
среда, 23 сентября 2015 г., 15:01:53 UTC+3 пользователь Sergei Kuzmin написал:
среда, 23 сентября 2015 г., 15:01:53 UTC+3 пользователь Sergei Kuzmin написал:
Reply all
Reply to author
Forward
0 new messages