RSS 2.0
Use for broad feed-reader and syndication compatibility.
Protocols guide
Connect the client that already fits the job.
Enable only the protocol the product needs, bind it, and test authentication, authorization, transport security, and path containment with the exact client.
- FTP + FTPS
- WebDAV-style
- RSS + Atom + JSON
Manage site files through FTP or FTPS.
- Configure a cloud store and an enabled site.
- Set the site's FTP flag and grant intentional site permissions to the user or group.
- Enable the FTP service globally and restart; it starts only when an FTP-enabled site exists.
- Connect with the Daptin username and password, then test list, upload, download, rename, directory creation, and delete.
- Use FTPS with a matching site certificate for protected transport.
the latest release includes the site-authorization fix documented for releases containing the published authorization fix. Keep affected older releases disabled or network-restricted.
Publish records for feed clients.
Map schema columns with FeedField values, then
request /feed/{entity}.rss, .atom, or
.json. Validate the content type, title, body,
publication date, record URL, stable ID, ordering, and permissions
with a real reader.
Atom
Use where Atom's entry and link structure fits the client.
JSON Feed
Use a JSON-native representation for application and automation clients.
WebDAV-style routes
Test the supported core file operations. Do not imply full CalDAV or CardDAV conformance.
WebDAV guide →Client matrix
Verify the exact protocol and client pair.
- Test FTP site login, allowed paths, denied paths, traversal attempts, and upload/download behavior.
- Use FTPS across untrusted networks and confirm the client validates the certificate.
- Exercise only the documented WebDAV-style operations; do not infer full CalDAV or CardDAV support.
- Open RSS, Atom, and JSON Feed output in the readers the product supports.
- Disable services the deployment does not need and retest authorization on the latest release.