-
Notifications
You must be signed in to change notification settings - Fork 22
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
Does this support Availability ? #10
Comments
Hi @signalarun! Yes, it supports the Availability feature as long as both the user making the event and the invited users all are in the same server. Here's an example: !(Availability example)[http://i.imgur.com/06LNPEq.png]
This snapshot was taken from the macOS Calendar.app while booking a sample event tomorrow, Friday 23.Nov.2018. I've tested this with Baïkal + Calendar.app, and with Baïkal with Thunderbolt + Lightning. Please expand details on your request so I can help you figure out what's happening with your set up. Which calendar software do you use? Cheers! pr3d |
I used Caldav4j library to access the Baikal docker. |
Ah, got it -- no idea. Do you have the server logs? They are in /var/log/nginx. Not sure about that Java library - I haven't used it. But I'm 100% sure that Baïkal reports the availability for all users registered in it. |
@signalarun - Is there an exception that you could show me too? Thanks! |
Exception in thread "main" java.io.IOException: Error executing method: org.osaf.caldav4j.methods.PutMethod@139ad8e HTTP response code: 409 |
OKi - does the response body have anything in it? This issue is on the CalDAV side, not the Docker side, happy to help if I can. Logs and the full response body, if available. I suggest that you try some interactive way of testing the responses after authenticating. Here's a great tool for checking what's happening during the exchanges: https://github.com/asciimoo/wuzz Cheers! |
One more thing: paste here the full HTTP request that your tool sends to the server. This error may be caused by an incorrect path. The full path should be something like:
Headers would be helpful too. Use wuzz to generate the requests so we can see what the server does. SoapUI might also be useful, but I prefer wuzz for expediency. Cheers! |
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns"> |
Hola. Two possibilities:
Check this out: http://sabre.io/dav/acl/ -- this explains how the ACLs work for SabreDAV (and for Baïkal since it leverages it). Where are you with the Cheers! |
The above two possibilities also not working. Can you give the link of working Baikal docker image that you use, so that I can try with that. |
The issues that you describe aren't caused by Baïkal. The client is providing wrong or incomplete data to the Sabre/CalDAV/Baïkal server. That's why I keep asking for logs or other diagnostic information. The Docker image you want for testing is |
The above two possibilities also not working. Can you give the link of working Baikal docker image that you use, so that I can try with that. |
I did in my previous entry. From Docker Hub: |
When I tried Availability on Baikel server with the docker image it gives operation not supported error.
The text was updated successfully, but these errors were encountered: