search

elrodo1 / pywebdav

Automatically exported from code.google.com/p/pywebdav
0 stars 0 forks source link

Windows XP mini-redirector #25

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What is the expected output? What do you see instead?
According to this document
http://greenbytes.de/tech/webdav/webdav-redirector-list.html no auth in
clear WindowsXP is supported. So i've run pywebdav as "davserver -M -D
/soft --host 0.0.0.0 --port 80 --no-auth "

But when I've tried to use net use * http://<ip_server>/<dir_name> it
throws with "System error 59 has occurred". An unexpected network error
occurred.

PanDAV (http://ivoras.sharanet.org/projects/pandav.html) work with this
configuration.

Server is running on Centos 5.2 and python 2.4

Original issue reported on code.google.com by Mikhail....@gmail.com on 14 Aug 2009 at 8:08

GoogleCodeExporter commented 8 years ago 
Can not reproduce that Pandav is working with this. It also fails for this 
configuration and Explorer shows nothing. How did you start Pandav?

I also could not find the cause for Redir not working correctly with PyWebDAV.

Original comment by spamsch@gmail.com on 16 Feb 2011 at 4:18

GoogleCodeExporter commented 8 years ago 
Issue 40 has been merged into this issue.

Original comment by spamsch@gmail.com on 16 Feb 2011 at 4:21

GoogleCodeExporter commented 8 years ago 
I think the problem lies in the authentication mechanism - Windows does not 
support Basic auth mechanism, only Digest

http://shon.org/blog/2010/03/04/howto-fix-windows-7-64bit-webdav/

I am fighting with the issue now...

Original comment by ladislav...@gmail.com on 7 Apr 2012 at 2:53

GoogleCodeExporter commented 8 years ago 
For every file and directory PyWebDAV includes a second "<D:propstat>" 
paragraph in it's PROPFIND response which has the "status" = "HTTP/1.1 404 not 
found". After removing this paragraph (by nginx reverse proxy filter 
techniques) the login with Windows7 MiniRedir is successful! Please tell me the 
reason for this second "propstat" paragraph. Other WebDav servers do not have 
this...

However, after successful login, MiniRedir still fails when trying to write 
(PUT) files. I analyzed the complete traffic going on between server and client 
for a write request and found out, that there is a PROPPATCH command in between 
LOCK and UNLOCK which is answered with "423 locked". The lock token is 
correctly present in an "If" header so as far as I can say this command should 
not be answered with "423" http error code! Please advise...

Original comment by andreas....@gmail.com on 12 Jan 2014 at 11:15