-
Notifications
You must be signed in to change notification settings - Fork 73
support all HTTP 3** redirects when dealing with well-known URIs #73
Comments
Hello @Zeriuno, just checking in to let you know that early this morning I published a new Flock update to Google Play which allows for use of the "Send debug log" feature from within the setup process. If you could update Flock and provide a debug log I think we'd have a good chance of figuring out how to make Flock play nicely with your Zimbra server, thanks! :) |
Here's a debug log! https://gist.github.com/anonymous/5262ce96f5a5bd8eb361 |
@Zeriuno sorry for taking so long to get back to you :/ The server tests fail on the very first test which is a I thought that 301 was the only allowed response according to RFC6764 however having just checked now I see that this is not the case. Flock should be patched to handle all 3** HTTP redirects, I will mark this issue as a bug now and try to get an update out soon so you can continue testing. Thanks for helping support the project by providing this log :) |
Not to worry, @rhodey. Thanks for finding the time to look at the log and thanks for finding the problem! I look forward to the fix and to finally be able to use Flock :) |
resolved by commit fc27816, will try to get in a Google Play Store release soon. Thanks for helping support the project :) |
Brilliant! I guess that my fellows at the same hosting provider now know what app to use! Thanks a lot, @rhodey! |
@Zeriuno no promise that your server will pass all the tests after this :P but I can say with confidence that this patch will make it possible to pass at least the first and I'll be glad to continue helping where I can. |
Trying to set up Flock with a CardDav account in Zimbra fails with error message:
"Server does not support CarDAV well-known URI or DAV: current-user-principal."
As agreed, I am filing a bug and I'll try to provide a debug log, when the feature will be available, in order to spot the cause of the issue!
The text was updated successfully, but these errors were encountered: