At this point, mini-redirector brings up the login prompt again and does so 3 times in total before failing to connect with an error saying the server cannot be found. Everything seems to work fine, my server accepts the login credentials and responds back with a 207 multistatus response with an "HREF" to the root directory. After entering the password, a new PROPFIND request is sent but this time with the authorization header. This brings up a login dialog for user and password. My server responds back with a 401 unauthorized. Then mini-redirector sends a PROPFIND method with a depth of 0. When I try to map the drive, an OPTIONS header is sent and my servers responds with a 200 OK. I have used Fiddler to analyze the network traffic and everything appears fine.
Microsoft webdav redirector Pc#
The strangest thing, is on my development PC where I wrote the server, I can connect just fine, however ANY other computer that tries to access the server, fails to connect with mini-redirector. It is working well with 3rd party WebDAV clients but does not work with Windows built-in mini-redirector when mapping a drive to the http location.
I wrote a custom WebDAV server that authenticates users from a database and serves a virtual file system based on records from a database.
0 kommentar(er)
