Mercurial > prosody-modules

view mod_cloud_notify_encrypted/README.md @ 6411:b00638d74f46

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mod_unified_push: Allow additional CORS headers for unified push (fixes #1985) - Request header "TTL" is mandated by the HTTP Push specification RFC 8030: https://datatracker.ietf.org/doc/html/rfc8030#section-5 - Firefox sends "Content-Encoding" with a HTTP form submission, so it is required when using the Unified Push testing tool at https://unifiedpush.org/test_wp.html (with the full URL being delivered by the UP-Example Android app) Adding both headers makes the Unified Push testing tool work from the browser. Resolves: https://issues.prosody.im/1985
author Christian Weiske <cweiske@cweiske.de>
date Sat, 21 Feb 2026 19:13:08 +0100
parents c83bfcc6ac0a
children
line wrap: on
line source

---
labels:
- 'Stage-Alpha'
summary: 'Support for encrypted payloads in push notifications'
...

Introduction
============

This module implements support for a [Encrypted Push Notifications](https://xeps.tigase.net//docs/push-notifications/encrypt/),
a custom extension to [XEP-0357: Push Notifications](https://xmpp.org/extensions/xep-0357.html).

It is planned that this will evolve to a XEP in the near future.

Details
=======

Add to `modules_enabled`, there are no configuration options.

When used with Prosody 0.12.x, it has an extra dependency on
[luaossl](http://25thandclement.com/~william/projects/luaossl.html)
which is available in Debian as
[`lua-luaossl`](https://tracker.debian.org/pkg/lua-luaossl) or via
`luarocks install luaossl`.

Prosody 13.0.x and trunk does not require this.

# Compatibility

  Prosody Version   Status
  ----------------- -----------------------------------
  13.0.x            Works
  0.12.x            Works (with `luaossl`, see above)