Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Folders are appearing as files #6126

Closed
cyberduck opened this issue Aug 2, 2011 · 10 comments
Closed

Folders are appearing as files #6126

cyberduck opened this issue Aug 2, 2011 · 10 comments
Assignees
@dkocher
Labels
bug fixed webdav WebDAV Protocol Implementation
Milestone
4.1.1

Comments

@cyberduck
Copy link
Collaborator

Angusbradley created the issue

Since the upgrade to 4.1, when I connect to our webdav server, the folder list displays as a list of unknown document types. When I click on a folder, it attempts to download it.

This was ok in 4.0

Many thanks

Angus

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Is it possible to get a test account on this server?

@cyberduck
Copy link
Collaborator Author

http://r0bcas7.myopenid.com/ commented

Same problem here with WebDAV on a Zope server. Cyberduck 4.0 works fine, since 4.1 all directories look like files.

Do you still need a test account? (my email is on here: http://www.mpiwg-berlin.mpg.de/en/staff/members/casties )

Thanks

Robert

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Sample response from Zope server to PROPFIND request.

<?xml version="1.0" encoding="UTF-8"?>
<d:multistatus xmlns:d="DAV:">
	<d:response>
		<d:href>/webdavtest/</d:href>
		<d:propstat xmlns:n="http://www.zope.org/propsets/default">
			<d:prop>
				<n:title>WebDAV test f[0xc3][0x83][0xc2][0xbc]r Cyberduck</n:title>
			</d:prop>
			<d:status>HTTP/1.1 200 OK</d:status>
		</d:propstat>
		<d:propstat xmlns:n="DAV:">
			<d:prop>
				<n:creationdate>1970-01-01T12:00:00Z</n:creationdate>
				<n:displayname>WebDAV test f[0xc3][0x83][0xc2][0xbc]r Cyberduck</n:displayname>
				<n:resourcetype>
					<n:collection/>
				</n:resourcetype>
				<n:getcontenttype/>
				<n:getcontentlength/>
				<n:source/>
				<n:supportedlock>
					<n:lockentry>
						<d:lockscope>
							<d:exclusive/>
						</d:lockscope>
						<d:locktype>
							<d:write/>
						</d:locktype>
					</n:lockentry>
				</n:supportedlock>
				<n:lockdiscovery>

</n:lockdiscovery>
				<n:getlastmodified>Wed, 17 Aug 2011 14:49:04 GMT</n:getlastmodified>
			</d:prop>
			<d:status>HTTP/1.1 200 OK</d:status>
		</d:propstat>
	</d:response>
	<d:response>
		<d:href>/webdavtest/acl_users</d:href>
		<d:propstat xmlns:n="DAV:">
			<d:prop>
				<n:creationdate>1970-01-01T12:00:00Z</n:creationdate>
				<n:displayname>U"
ser Folder</n:displayname>
				<n:resourcetype/>
				<n:getcontenttype/>
				<n:getcontentlength/>
				<n:source/>
				<n:supportedlock>
					<n:lockentry>
						<d:lockscope>
							<d:exclusive/>
						</d:lockscope>
						<d:locktype>
							<d:write/>
						</d:locktype>
					</n:lockentry>
				</n:supportedlock>
				<n:lockdiscovery>

</n:lockdiscovery>
				<n:getlastmodified>Wed, 17 Aug 2011 14:46:48 GMT</n:getlastmodified>
			</d:prop>
			<d:status>HTTP/1.1 200 OK</d:status>
		</d:propstat>
	</d:response>
	<d:response>
		<d:href>/webdavtest/bild1.png</d:href>
		<d:propstat xmlns:n="http://www.zope.org/propsets/default">
			<d:prop>
				<n:title/>
				<n:content_type>image/png</n:content_type>
			</d:prop>
			<d:status>HTTP/1.1 200 OK</d:status>
		</d:propstat>
		<d:propstat xmlns:n="DAV:">
			<d:prop>
				<n:creationdate>1970-01-01T12:00:00Z</n:creationdate>
				<n:displayname>bild1.png</n:displayname>
				<n:resourcetype/>
				<n:getcontenttype>image/png</n:getcontenttype>
				<n:getcontentlength>548358</n:getcontentlength>
				<n:source/>
				<n:supportedlock>
					<n:lockentry>
						<d:lockscope>
							<d:exclusive/>
						</d:lockscope>
						<d:locktype>
							<d:write/>
						</d:locktype>
					</n:lockentry>
				</n:supportedlock>
				<n:lockdiscovery>

</n:lockdiscovery>
				<n:getlastmodified>Wed, 17 Aug 2011 14:48:51 GMT</n:getlastmodified>
			</d:prop>
			<d:status>HTTP/1.1"
 200 OK</d:status>
		</d:propstat>
	</d:response>
	<d:response>
		<d:href>/webdavtest/folder1/</d:href>
		<d:propstat xmlns:n="http://www.zope.org/propsets/default">
			<d:prop>
				<n:title/>
			</d:prop>
			<d:status>HTTP/1.1 200 OK</d:status>
		</d:propstat>
		<d:propstat xmlns:n="DAV:">
			<d:prop>
				<n:creationdate>1970-01-01T12:00:00Z</n:creationdate>
				<n:displayname>folder1</n:displayname>
				<n:resourcetype>
					<n:collection/>
				</n:resourcetype>
				<n:getcontenttype/>
				<n:getcontentlength/>
				<n:source/>
				<n:supportedlock>
					<n:lockentry>
						<d:lockscope>
							<d:exclusive/>
						</d:lockscope>
						<d:locktype>
							<d:write/>
						</d:locktype>
					</n:lockentry>
				</n:supportedlock>
				<n:lockdiscovery>

</n:lockdiscovery>
				<n:getlastmodified>Wed, 17 Aug 2011 14:50:18 GMT</n:getlastmodified>
			</d:prop>
			<d:status>HTTP/1.1 200 OK</d:status>
		</d:propstat>
	</d:response>
</d:multistatus>

@cyberduck
Copy link
Collaborator Author

@dkocher commented

As one can see from the above output, the Zope server is not WebDAV compliant. The elements in the property collection should be in the default DAV: namespace and not in the proprietary http://www.zope.org/propsets/default namespace which should only be used for custom properties not part of the RFC. Please report as a bug to the Zope development team.

@cyberduck
Copy link
Collaborator Author

http://r0bcas7.myopenid.com/ commented

Replying to [comment:5 dkocher]:

As one can see from the above output, the Zope server is not WebDAV compliant. The elements in the property collection should be in the default DAV: namespace and not in the proprietary http://www.zope.org/propsets/default namespace which should only be used for custom properties not part of the RFC.

I am no expert in DAV but the <n:resourcetype><n:collection/></n:resourcetype> which I assume indicates a Folder is in the DAV: namespace. Only title and content_type are not in this namespace.

Please report as a bug to the Zope development team.

Even if the XML were wrong (I'm not sure it is), couldn't Cyberduck work the same way as it did until V4.1? All other WebDAV clients I use work fine with Zope.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Thanks for your comment. I was skipping over the document too fast. The namespace is right and should be recognized.

@cyberduck
Copy link
Collaborator Author

http://r0bcas7.myopenid.com/ commented

Replying to [comment:7 dkocher]:

Thanks for your comment. I was skipping over the document too fast. The namespace is right and should be recognized.

The XML is ugly, I agree :-) Its a bad idea to use the same namespace abbreviation for different namespaces on different elements.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I can confirm this is a bug in Cyberduck/Sardine. Only the first propstat element is taken into account.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Fix commited to Sardine.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 0ad52fb. Thanks for the test environment and bringing this to my attention.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug fixed webdav WebDAV Protocol Implementation
Projects
None yet
Milestone
4.1.1
Development

No branches or pull requests
2 participants
@dkocher @cyberduck