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

No files visible connecting to box.net #6538

Closed
cyberduck opened this issue Feb 10, 2012 · 11 comments
Closed

No files visible connecting to box.net #6538

cyberduck opened this issue Feb 10, 2012 · 11 comments
Assignees
@dkocher
Labels
bug fixed webdav WebDAV Protocol Implementation
Milestone
4.3

Comments

@cyberduck
Copy link
Collaborator

Mknart created the issue

  1. New connection:
    Server: www.box.net

Port: 443

User: (user)

Pass: (pass)

Path: /dav/

=>
Generated URL: https://(user)@www.box.net:443/dav

  1. Connection complete.
    Path is /dav.
    No files or subdirectories visible.

  2. Click path, go to root (from /dav to /).
    Login window pops up that points to www.box.com:443.box.net/dav ???

Fill in (user) and (pass)

/dav root directory visible

  1. Doubleclick subfolder in list.
    Path is /dav/subfolder.

No files visible.

Running Windows 7.
@cyberduck
Copy link
Collaborator Author

@dkocher commented

I can replicate the issue.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#6538 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

7846d58 commented

It worked for me after some changes:

  • WebDAV (HTTP/SSL)
  • Server: box.net (ATTENTION: net instead of com)
  • Port: 443
  • give Username & Password
  • Path:

Pressung Connect shows a warning about an Certificate (maybe because box.net different from box.com). I accepted it.

I saw the dir listing.
When I clicked on a folder, he asks me for credentials again. I tell'em and after then, all works fine. I dunno why it works but it does. I didn't do a deeper analysis on it.

@cyberduck
Copy link
Collaborator Author

903e660 commented

Hi David,

If you contact me here at Box we can help figure out what's going on here and resolve this.  Thanks,

    --Matthew

@cyberduck
Copy link
Collaborator Author

ffdc734 commented

I confirm that with the new version it does not work anymore.
I used ver 4.0.2 for osx, and it worked like a charm to connect to box.net using webdav.
I then upgraded to the latest version (4.2.1) and it doesn't work anymore.
It keep asking for username and pwd. Then, once logged in, it pretends to go to https://www.box.net/dav
But my files are in https://www.box.net/ [no /dav/ ...]
this breaks everything...
Switched back to 4.0.2
Hope this helps

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#6752 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Another box.com interoperability issue in #6528.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Another box.com interoperability issue in #6529.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

See also #6767.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Changes in authentication handler in 2423aa6 will possibly fix this. Please reopen if still an issue with the current snapshot build.

@cyberduck
Copy link
Collaborator Author

903e660 commented

Box has changed their WebDAV URL to https://dav.box.com/dav. This new version at this URL should have better interoperability that the previous one. Thanks.

@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.3
Development

No branches or pull requests
2 participants
@dkocher @cyberduck