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

Not a valid DAV response error message when listing directory #8171

Closed
cyberduck opened this issue Aug 12, 2014 · 5 comments
Closed

Not a valid DAV response error message when listing directory #8171

cyberduck opened this issue Aug 12, 2014 · 5 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Aug 12, 2014

4568140 created the issue

I set up an account on Magento's Big Commerce. Set up the WebDAV connection according to the instructions from Big Commerce. The login is successful, but then I get this error message:

LISTING DIRECTORY FAILED (/)
NOT A VALID DAV RESPONSE

I contacted the support at Big Commerce. They could not duplicate the problem on their end. Any idea of what might be happening and how I can correct this?

Below I've copied the event log:

HEAD / HTTP/1.1
Host: landofodds.mybigcommerce.com
Connection: Keep-Alive
User-Agent: Cyberduck/4.4.3 (14140) (Windows 7/6.1) (x86)
Authorization: Basic d2FycmVuQGxhbmRvZm9kZHMuY29tOjdlYzg4YWYzZjZhMDA4NzIxN2JiOTY5NjgwYTc0MzQ3IA==
HTTP/1.1 200 OK
Server: nginx
Date: Tue, 12 Aug 2014 14:42:47 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: SHOP_SESSION_TOKEN=2p44unm7dri1tpdpth9vee38n4; expires=Tue, 19-Aug-2014 14:42:46 GMT; path=/; domain=.store-cvpk08sj.mybigcommerce.com; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Encoding: gzip
PROPFIND / HTTP/1.1
Depth: 1
Content-Type: text/xml; charset=utf-8
Content-Length: 99
Host: landofodds.mybigcommerce.com
Connection: Keep-Alive
User-Agent: Cyberduck/4.4.3 (14140) (Windows 7/6.1) (x86)
Authorization: Basic d2FycmVuQGxhbmRvZm9kZHMuY29tOjdlYzg4YWYzZjZhMDA4NzIxN2JiOTY5NjgwYTc0MzQ3IA==
HTTP/1.1 200 OK
Server: nginx
Date: Tue, 12 Aug 2014 14:42:49 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: SHOP_SESSION_TOKEN=qe7bsvds484l5r8pspdkgdcfa6; expires=Tue, 19-Aug-2014 14:42:47 GMT; path=/; domain=.store-cvpk08sj.mybigcommerce.com; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Encoding: gzip
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 12, 2014

@dkocher commented

Have you followed their instructions and downloaded the provided connection profile? You should set /dav in the Default Path of the bookmark.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 9, 2015

@dkocher commented

Fixed in 19f4555. Duplicate for #8712.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 28, 2015

307866b commented

This same issue is happening for me. I'm using a mac which I think might be the issue as I have the latest version of cyberduck installed. Please help!

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 29, 2015

@dkocher commented

Replying to [comment:5 ysayed]:

This same issue is happening for me. I'm using a mac which I think might be the issue as I have the latest version of cyberduck installed. Please help!

Please open a new issue with the transcript from the log drawer (⌘-L) attached.

@cyberduck cyberduck closed this May 29, 2015
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 4, 2015

@dkocher commented

#8857 closed as duplicate.

@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.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants