WebDAV Push Implementation Questions

[Svagtlys]

I'm working out WebDAV Push as an alternative to webhooks, and already hitting questions :)

For the URL to POST the subscription XML to, does the URL include the full /frontend/user/MyUser/calendar/<random-calendar-id-here>? I happened to notice the JSON under the Timezone section has "subscription_url":null in it, not sure if this is related to the WebDAV-Push implementation?

Also, I assume I'll need to authenticate when I subscribe, is that done via basic auth? Can I use an app password generated by the user?

[lennart-k]

So the URL is like the CalDAV resource, i.e. /caldav/principal/MyUser/<random-calendar-id-here>
The subscription_url is not related to webdav push, that's an external link if the calendar is actually a subscription to some external calendar.

You are right with authentication, you do Basic authentication with your username and app token.

[Svagtlys]

Does your implementation support VAPID?

[lennart-k]

At the moment no

[Svagtlys]

Rustical is giving me this error after trying to subscribe to WebDAV-push

An error occured sending out a push notification: OpenSSL error: error:08000066:elliptic curve routines:ossl_ec_GFp_simple_oct2point:invalid encoding:crypto/ec/ecp_oct.c:295:

Would you say that this means I got the public-key wrong in my subscription?