c4fecc201bbf4899354e63696e611f01d20cdd89
two bugs, both of which iOS reports as "Cannot connect using SSL" — a message about TLS for a problem that has nothing to do with TLS. the certificate was never involved. the well-known routes were registered with .get. RFC 6764 §6 has the client probe the well-known URI with the method it actually intends to use, and iOS sends PROPFIND — which fell through to the SPA catch-all and 404'd. they answered correctly in a browser, which is why they looked healthy. hono's cors() answers every OPTIONS itself as a preflight and never calls the route beneath it, so OPTIONS /dav/ returned a bare 204 with no DAV header. OPTIONS is not a preflight to a DAV client — it is how the client asks what the server can do, and iOS refuses an account whose server does not advertise calendar-access. cors now skips the DAV paths entirely; a CalDAV client is not a browser and has no origin to check. verified from the public internet: PROPFIND on both well-known paths 301s to /dav/, and an authenticated OPTIONS now returns `DAV: 1, 2, 3, calendar-access, addressbook, extended-mkcol`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Description
No description provided
42 MiB
Languages
TypeScript
90.9%
Shell
4.7%
JavaScript
4.1%
CSS
0.2%
HTML
0.1%