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

Error: NOT A VALID DAV RESPONSE when uploading to large image folder #8857

Closed
cyberduck opened this issue Jun 2, 2015 · 4 comments
Closed

Error: NOT A VALID DAV RESPONSE when uploading to large image folder #8857

cyberduck opened this issue Jun 2, 2015 · 4 comments
Assignees
@dkocher
Labels
bug high priority thirdparty Issue caused by third party webdav WebDAV Protocol Implementation
Milestone
4.7

Comments

@cyberduck
Copy link
Collaborator

307866b created the issue

Opening a new ticket with the same issues as Ticket #8171

I am working with Demandware and have contacted them but they are unable to find anything. I have the latest version of cyberduck but am on a mac which may be the issue. Including all info from previous ticket.

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

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please update to the latest version which is currently 4.7. The transcript shows you are running version 4.4.3. Use Help → Check for Update… to update.

@cyberduck
Copy link
Collaborator Author

307866b commented

The transcript is from the old ticket. I just added it to the new ticket for reference. I am running the latest version of Cyberduck 4.7 and am still receiving the same error.

@cyberduck
Copy link
Collaborator Author

2dc83a7 commented

Hi, Having similar issue also on version 4.7. Issue seems to be specific to one directory that includes files larger then 10MB. One file is 47MB. Other directories on the same server work fine. Is there a work around to access this folder?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please report this issue to the server vendor. The server is responding with an invalid XML response.

@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 high priority thirdparty Issue caused by third party webdav WebDAV Protocol Implementation
Projects
None yet
Milestone
4.7
Development

No branches or pull requests
2 participants
@dkocher @cyberduck