Connection failed to WebDAV: Status line was: HTTP/1.1 200 :: Support Forum

qlamenx Guest

Connection failed to WebDAV: Status line was: HTTP/1.1 200

2025-04-05 09:26

Hi all,

Trying to connect to a WebDAV server, but I get this error message:

Invalid HTTP status line in status element at line 10 of response:
Status line was: HTTP/1.1 200

How can I solve this?
Kindly appreciated your support!

Reply with quote

martin◆ Site Admin
Joined:: 2002-12-10
Posts:: 41,929
Location:: Prague, Czechia

Re: Connection failed to WebDAV: Status line was: HTTP/1.1 200

2025-04-07

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Reply with quote

huemanTX
Joined:: 2025-04-07
Posts:: 3
Location:: US

Same error

2025-04-07 17:15

Seeing the same error on all our WebDAV sites. Log attached.

WinSCP.log (12.9 KB)

Reply with quote

martin◆ Site Admin
Joined:: 2002-12-10
Posts:: 41,929
Location:: Prague, Czechia

Re: Same error

2025-04-08

@huemanTX: Thanks. It's due to this change in the neon library:
https://github.com/notroj/neon/commit/b132c8377200e7ea76364125aff43e79f475e6b1
It's bit of a gray zone. The status response HTTP/1.1 200 without "reason phrase" does not strictly conform to the HTTP 9112. Which, while does not require the "reason phrase" as such, requires a space after the "status code". What your server's response lacks.
https://datatracker.ietf.org/doc/html/rfc9112#name-status-line
Anyway, I understand that it is a regression and I'll look into it.
What WebDAV server is that?

Reply with quote

martin◆ Site Admin

Re: Same error

2025-04-08

Also, please post log on Debug 2-level.

Reply with quote

huemanTX
Joined:: 2025-04-07
Posts:: 3
Location:: US

Re: Same error

2025-04-08 15:37

Hello Martin. Thanks for the reply. New log file attached. I'm not certain about the WebDAV server. These are vendor hosted connections. Running Apache Tomcat in AWS. I can forward this information on to them.

WinSCP2.log (37.03 KB)

Reply with quote

martin◆ Site Admin
Joined:: 2002-12-10
Posts:: 41,929
Location:: Prague, Czechia

Re: Same error

2025-04-09

Thanks for the log. So I was wrong. The space is there. It's likely swallowed while parsing the XML response. Nothing wrong on the server side.

I've reported this to the neon project:
HTTP status parsing in WebDAV <status> without reason phrase regression · Issue #188 · notroj/neon

Reply with quote

martin◆ Site Admin
Joined:: 2002-12-10
Posts:: 41,929
Location:: Prague, Czechia

Re: Same error

2025-04-15

I have added this issue to the tracker:
Issue 2368 – Failure when parsing WebDAV <status> without reason phrase

I'll be sending you an email with a development version of WinSCP to the address you have used to register on this forum.

Reply with quote

huemanTX

Re: Same error

2025-04-15 15:12

Tested and looks to be working fine now.

Thanks very much.

Reply with quote

OD Guest

Re: Same error

2025-04-16 08:59

Hi Martin,
I have multiple clients that can not connect due to the same error. Is there a specific WinSCP release in which this will be resolved?

Reply with quote

CV USER
Joined:: 2025-04-17
Posts:: 1

same error

2025-04-17 09:46

Hello,

It looks like we have the same issue in WinSCP.
See the attachment that i added.
Is this a common issue and is there a solution already?

afbeelding1.PNG (82.79 KB)

Reply with quote

martin◆ Site Admin

Re: same error

2025-04-17

If you follow the thread and tracker link above, you will see that this has been fixed already and the fix will be included in upcoming WinSCP 6.5.1. Meanwhile, you can downgrade to 6.3.8.

Reply with quote