Failed to authorize webdav when password longer than 21 #170
Comments
|
Oh my, this is a very thorough bug report, thank you! First, i assume that this is the same bug as #157 and the same as in this discussion: #159. I havent gotten around to figure out why the password wasnt beeing handled correctly, so your report is invaluable. But i am curious, how did you figure out that 21 character boundary? :D |
|
lmao, after found it may be related with password, before submitting issue, I try multi times. With dufs as local webdav server, a new attempt is not so hard. ;) Thanks for your quick response, and feel free to close as duplicated. |
|
I'll keep it open until it is fixed ;) |
|
@leafee98 Could you do me a favor? Could you check what happens if you use a username that is longer than 21 chars? Especially what the server recieves? I dont have a handy remote available at the moment that would easily allow me to test this. (In the future, ill likely check out dufs in detail, it looks interesting for such debugging purposes) |
|
It work fine with 22 And the response, which is a webdav response without any error. The |
|
It still working even with 65 characters. Just mention me whenever you need, I will do things in my ability at the time I see it. :D |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Round Sync are you using (About -> App version)?
v2.2.2 from GitHub release
What is your Android version, phone model and manufacturer?
Android 13, Lineage OS 20
Which steps are required to reproduce this issue?
Start a webdav service, I'm using dufs as example, this will serve
/tmp/test-webdavand create two users, u21 with 21ps as password and u22 with 22ps as password.Then create two webdav remotes on Round-Sync, u21 and u22.
Just browser those two remotes on Round-Sync, u21 works fine, and u22 error.
Android/data/de.felixnuesse.extract/files/logs/log.txtshow as401 Unauthorized(time doesn't match because I collected these information with multi attempts):Information from tcpdump
For u21:
For u22:
Authorization header for u21 is
Basic dTIxOnBwcHBwcHBwcHBwcHBwcHBwcHBwcA==, decode base64 gotu21:ppppppppppppppppppppp, while u22 isBasic dTIyOg==and decode gotu22:What is your configuration (
rclone.conf)?Does the same issue also occur when using the same configuration on a PC or in Termux?
Yes, u22 not work with the same config, tcpdump shows the Authorization header is
Basic.dTIyOg==, same as tcpdump output with u22 on Round-Sync.But if I create a new config, it will work, for u22 the new config created as follow.
Rclone version as follow.
The text was updated successfully, but these errors were encountered: