WebDAV redirector makes strange requests in Windows 10

Question

WebDAV redirector makes strange requests in Windows 10

Neperian Diamondback 25

I noticed that when I access a WebDAV resource through the file manager, I get horrible performance, and looking at the Apache logs on the server I see some oddities come through.

Requests from my authenticated user (the server requires Negotiate) are interspersed with requests from my machine credentials. ?!?! Why should the system be asking for the same file properties as the user, at the same time?
Sometimes it capitalizes the first part of the WebDAV path in the request. The Apache server, of course, responds that the method is not allowed because the uppercase path is not the same as the lowercase path. Why would it suddenly start uppercasing the path?

1 answer

Your answer

Answer 1

Limitless Technology 44,766

Hello there,

You can use packet monitor to exactly analyse the request and make the call.

Packet Monitor (Pktmon) is an in-box, cross-component network diagnostics tool for Windows. It can be used for packet capture, packet drop detection, packet filtering and counting. The tool is especially helpful in virtualization scenarios, like container networking and SDN, because it provides visibility within the networking stack. It is available in-box via the pktmon.exe command and via Windows Admin Center extensions.

https://learn.microsoft.com/en-us/windows-server/networking/technologies/pktmon/pktmon

Hope this resolves your Query !!

--If the reply is helpful, please Upvote and Accept it as an answer--

Neperian Diamondback 25 Reputation points

2023-05-05T17:44:56.4866667+00:00

Does Packet Monitor have the ability to analyze why Webdav Redirector makes the decisions it does? What I read suggests that it's a local version of Wireshark (and even supports Wireshark capture format). I watched the Windows side with Wirshark and the server side by looking at the access logs. I can say that I see the requests being made, but I am baffled as to why it makes some of its requests.

Like, does it use machine creds to do local caching or something like that? And if so, can that be turned off for Webdav Redirector? For now I made the machine creds equivalent to the user that most commonly used that system, but that's obviously not a good solution. Is there a harm in simply refusing requests from the machine itself?

And then the capitalized URL part is especially weird. I see those requests on both sides, with the capitalization. I can't see any scenario where that would be a good choice, so it would be nice to know the decision process that led Webdav Redirector to that.

Share via

WebDAV redirector makes strange requests in Windows 10

1 answer

Your answer