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

Error when accessing via client #19

Closed
badengineer opened this issue Oct 20, 2011 · 1 comment
Closed

Error when accessing via client #19

badengineer opened this issue Oct 20, 2011 · 1 comment

Comments

@badengineer
Copy link

I'm using Ubuntu, when i try to access via client (i tried LibreOffice and filesystem mount "sudo mount.davfs -t "http://localhost:8000" "FOLDER") I get the following error:

jsDAV server running on '127.0.0.1' port 8000
INFO: invoking method 'GET'
INFO: sending header: 200, { 'Content-Type': 'text/html; charset=utf-8' }
INFO: writing body: '

... some html...

argument after event: true
INFO: invoking method 'OPTIONS'
argument after event: null
INFO: sending header: 200, { Allow: 'OPTIONS,GET,HEAD,DELETE,PROPFIND,PUT,PROPPATCH,COPY,MOVE,REPORT',
'MS-Author-Via': 'DAV',
'Accept-Ranges': 'bytes',
'X-jsDAV-Version': undefined,
'Content-Length': 0,
DAV: '1,3,extended-mkcol,2' }
INFO: writing body: 'undefined'
INFO: invoking method 'PROPFIND'
argument after event: null
INFO: data received
propfind xmlns="DAV:">
getetag xmlns="DAV:"/>
getcontentlength xmlns="DAV:"/>
creationdate xmlns="DAV:"/>
getlastmodified xmlns="DAV:"/>
resourcetype xmlns="DAV:"/>
executable xmlns="http://apache.org/dav/props/"/>
/prop>

Segmentation fault

NOTE: OPENING TAGS OF XML REMOVED MANUALLY FOR THIS POST

Followed the problem down to the o3-xml library. Is this a bug or do I have a wrong understanding of the capabilities of jsDAV?

mikedeboer pushed a commit that referenced this issue May 23, 2012
Add support for tick searches, return options content back to C9 results
@mikedeboer
Copy link
Owner

jsDAV has changed A LOT in a year. Current release is v0.3.0. Closing this issue, because it cannot be reproduced.

If you find this decision to be in error, please reopen the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants