forks/baikal
1
0
Fork 0
Code Releases Activity

Update TROUBLESHOOTING.md

Browse source 
Former-commit-id: adc863da61
This commit is contained in:
Jérôme Schneider 2012-08-21 14:01:16 +03:00
parent 2c9b764f8d
commit 6a3369e926
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
TROUBLESHOOTING.md
View file

@ -25,25 +25,25 @@ To troubleshoot user auth / data access, you may use curl to debug server respon
(Be sure that the username exists, has the right password set, and has a calendar named default first).
If you see this, auth works for this username/password/calendar, so it has to be client-related:
<s:message>GET is only implemented on File objects</s:message>
GET is only implemented on File objects
If you see this, password is wrong (case-sensitive) (despite the message indicating that it's the username):
<s:message>Incorrect username</s:message>
Incorrect username
If you see this, username is wrong:
<s:message>The supplied username was not on file</s:message>
The supplied username was not on file
If you see this, auth works but the "principals" part of the URL is wrong (the /username/ after "calendars" in the URL):
<s:message>Principal with name username not found</s:message>
Principal with name username not found
If you see this, auth works but the calendar does not exist for this user:
<s:message>Calendar with name 'defaults' could not be found</s:message>
Calendar with name 'defaults' could not be found
If you see this, auth works and the calendar exists, but the provided user has no permission to access this calendar:
<s:exception>Sabre_DAVACL_Exception_NeedPrivileges</s:exception>
Sabre_DAVACL_Exception_NeedPrivileges
If you see one of these, the URL is not well formed / invalid:
<s:message>File not found: XXXXX in 'root'</s:message>
File not found: XXXXX in 'root'
Or
The requested URL XXXXX was not found on this server.