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
Woops, something's gone wrong! The CardDAV server returned the http status code 500. #1017
Comments
/cc @DeepDiver1975 |
I think z-push specific questions are out of scope for this issue tracker, unless you can track down what the server actually sent back (other than a 500 status code, there should be a response body with more info) |
@evert Are you suggesting this a z-push bug? So far all I can say it's a regression introduced by the update from 3.2.0 to 3.2.1 that's why I thought it's best to start filing that against sabre-dav. That said, can you give me pointers how I can provide you with the information you asked for |
Not necessarily, but if an issue is reported and it's in the form "I'm using tool X and I'm getting an error", I think the burden of proof is a bit on the reporter to make sure that all the information is provided. In the past there's been a lot of owncloud reports in this project for example, and the default stance there too has been: Go talk to owncloud first and let their devs figure out if it's a sabre/dav problem.
I would dig into z-push and figure out if you can extract more information from that tool. There's also a possibility that the actual error ended up in a php or webserver error log. |
Request
Response
|
Adding a debug print at https://github.com/sabre-io/dav/blob/master/lib/CardDAV/Xml/Filter/AddressData.php#L55 I get the following for $elems:
Notice how there is no |
Commenting out |
@DeepDiver1975 any idea what's going wrong there and how this can be fixed? |
…05c2fa8023f913 Properly parse carddav address-data - fixes #1017
@DeepDiver1975 j4i #1025 fixed this problem for me, thx. |
I use sabre-dav in combination with z-push (http://z-push.org/).
Since the update of sabre-dav from 3.2.0 to 3.2.1, z-push is broken and I get error messages like the following in the z-push log:
Running a git bisec points at 73065c3 as the first faulty commit. This was added for #889
The text was updated successfully, but these errors were encountered: