DAV dir listing stalled on Word temp files

[cyberduck]

3b43c93 created the issue

I have a setup where LAN users connect to a shared dir using SMB and WAN user connect over DAV.

If a lan user has an MS Word doc open on the shared directory a temp file in the form of:

~$D filename.doc

is created. Cyberduck at that point can no longer refresh the directory listing for wan users using DAV. Once the lan user closes the Word doc wan DAV listing is back to normal.

CD 3.2.1 connecting to an IIS DAV server over SSL.

Leopard Finder DAV can list the directory OK (but leopard DAV is dodgy at best)

[cyberduck]

@dkocher commented

Can you post the error message if any (including the transcript) and and any related output in the console.log (/Applications/Utilities/Console.app).

Is it possible to get access to the server to debug the issue?

[cyberduck]

3b43c93 commented

console output generated. This is the result of this scenario:

• no doc open
• cyberduck to dir, list dir ok
• open doc on LAN
• refresh
• loops

Unable to post console because your Akismet scanner says it is spam. Will e-mail.

[cyberduck]

@dkocher commented

Replying to [comment:2 john@…]:

console output generated.

3/19/09 11:45:52 AM [0x0-0x12d92d8].ch.sudo.cyberduck[17586] Exception in thread "Background" java.lang.NullPointerException 
3/19/09 11:45:52 AM [0x0-0x12d92d8].ch.sudo.cyberduck[17586]  at ch.cyberduck.core.dav.DAVPath.list(DAVPath.java:165) 
3/19/09 11:45:52 AM [0x0-0x12d92d8].ch.sudo.cyberduck[17586]  at ch.cyberduck.core.AbstractPath.childs(AbstractPath.java:104) 
3/19/09 11:45:52 AM [0x0-0x12d92d8].ch.sudo.cyberduck[17586]  at ch.cyberduck.core.AbstractPath.childs(AbstractPath.java:91) 
3/19/09 11:45:52 AM [0x0-0x12d92d8].ch.sudo.cyberduck[17586]  at ch.cyberduck.ui.cocoa.CDBrowserController$5.run(CDBrowserController.java:690) 
3/19/09 11:45:52 AM [0x0-0x12d92d8].ch.sudo.cyberduck[17586]  at ch.cyberduck.ui.cocoa.CDWindowController$1.run(CDWindowController.java:76) 

It looks like the resourcetype property is missing for this collection entry.

[cyberduck]

@dkocher commented

The actual response is

<a:multistatus xmlns:b="urn:uuid:c2f41010-65b3-11d1-a29f-00aa00c14882/" xmlns:c="xml:" xmlns:a="DAV:">
	<a:response>
		<a:href>https://central.bmdc.org/cyberduck/</a:href>
		<a:propstat>
			<a:status>HTTP/1.1 200 OK</a:status>
			<a:prop>
				<a:displayname>cyberduck</a:displayname>
				<a:getcontentlength b:dt="int">0</a:getcontentlength>
				<a:getcontenttype>application/octet-stream</a:getcontenttype>
				<a:resourcetype><a:collection/></a:resourcetype>
				<a:getlastmodified b:dt="dateTime.rfc1123">Fri, 20 Mar 2009 12:05:16 GMT</a:getlastmodified>
			</a:prop>
		</a:propstat>
	</a:response>
	<a:response>
		<a:href>https://central.bmdc.org/cyberduck/foo.doc</a:href>
		<a:status>HTTP/1.1 403 Forbidden</a:status>
	</a:response>
	<a:response>
		<a:href>https://central.bmdc.org/cyberduck/~$D%20filename.doc</a:href>
		<a:propstat>
			<a:status>HTTP/1.1 200 OK</a:status>
			<a:prop>
				<a:displayname>~$D filename.doc</a:displayname>
				<a:getcontentlength b:dt="int">0</a:getcontentlength>
				<a:getcontenttype>application/msword</a:getcontenttype>
				<a:resourcetype/>
				<a:getlastmodified b:dt="dateTime.rfc1123">Fri, 20 Mar 2009 08:21:06 GMT</a:getlastmodified>
			</a:prop>
		</a:propstat>
	</a:response>
</a:multistatus>

causing a null pointer for responses that have a Forbidden status and miss any propstat dictionary.

[cyberduck]

@dkocher commented

In 058b229.