Mercurial > prosody-modules
view mod_limits_exception/README.md @ 6411:b00638d74f46
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 | 12a2989c7cc1 |
| children |
line wrap: on
line source
--- labels: - Stage-Obsolete summary: Allow specified JIDs to bypass rate limits --- This module allows you to configure a list of JIDs that should be allowed to bypass rate limit restrictions. It is designed for Prosody 0.11.x. Prosody 0.12.x supports this feature natively. ## Configuration First, enable this module by adding `"limits_exception"` to your `modules_enabled` list. Next, configure a list of JIDs to exclude from rate limiting: ``` unlimited_jids = { "user1@example.com", "user2@example.net" } ``` ## Compatibility Made for Prosody 0.11.x only. Using this module with Prosody trunk/0.12 may cause unexpected behaviour.
