WebDAV

Oboku lets you use WebDAV server to synchronize your books but you need to make sure your WebDAV server is configured in a way that works.

CORS

Your server needs to returns a valid CORS. You cannot use a wildcard * because oboku needs to sends credentials. This means you will have to specify the origin. If you use the cloud version, you can use https://app.oboku.me. If you use the self host version, use whatever host / ip you use.

OPTIONS

Your browser will not sends the credentials for a preflight request (see https://fetch.spec.whatwg.org/#http-cors-protocol). This means your server must returns a valid HTTP status when responding to OPTIONS requests. This is a common issue with synology WebDAV server which requires authentication even for OPTIONS requests.

You can configure a reverse proxy in front of your WebDAV server and intercept OPTIONS requests to return a 200 status

Connectors

Connectors are shareable connection configuration that you can use for both data sources and content access.

UURID

You can read more about UURID here. Unlike Google Drive or Dropbox which already have a unique ID for each of their resources (UUID), webDAV does not. We try to build a RUI following this scheme:

webdav://{hostname}:{filename}