WebDAV 5.21 authentication error "could not handle non-ASCII username in Digest challenge"

Advertisement

MrWhipple
Guest

WebDAV 5.21 authentication error "could not handle non-ASCII username in Digest challenge"

I use WinSCP to connect via WebDAV to my employer's store on the BigCommerce ecommerce platform.

Starting with v. 5.21, when I try to connect, I receive the authentication error message,
Could not authenticate to server: could not handle non-ASCII username in Digest challenge / Connection failed
I rolled back to v. 5.19.6 and I'm able to authenticate without any problems.

I've attached my log file. I've replaced some sensitive data (store URL, username, etc.) with UPPERCASE GENERIC TEXT.

Additional info:
  • Microsoft Windows 10 Pro v. 10.0.19044 Build 19044
  • GUI w/Explorer interface

winscp-authentication-failed.png

Reply with quote

Advertisement

yhummo
Joined:
Posts:
1

We are BigCommerce customer -
To the letter, experience the same issue and receive the same error messaging as the OP.
Attached log file following the same methodology specified by OP.

Edition: Windows 10 Enterprise
Version: 21H2
OS build: 19044.1706
Experience: Windows Feature Experience Pack 120.2212.4170.0
GUI: Explorer Interface

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
37,591
Location:
Prague, Czechia

Re: WebDAV 5.21 authentication error "could not handle non-ASCII username in Digest challenge"

Thanks for your reports. Please post logs from 5.19.6 for comparison.

Reply with quote

martin
Site Admin
martin avatar

So does your username really contain non-ASCII characters? Were your given that username? Or did you chose it?

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
37,591
Location:
Prague, Czechia

@MrWhipple: Thanks for your response.

Can you send me an email, so I can send you back a development version of WinSCP for testing? Please include a link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

You will find my address (if you log in) in my forum profile.

Reply with quote

jeking
Guest

Same problem, any update?

I have this same problem and have also reverted back to 5.19.6.
5.21.1 has this same problem. I tried it, got the same error, reverted back to 5.19.6

Reply with quote

Advertisement

Advertisement

You can post new topics in this forum