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

# Introduction

This module exposes users [microblogging][xep277] on Prosodys built-in HTTP server.

# Usage

With default HTTP settings, the microblog of `user@example.com` would be
seen at `https://example.com:5281/atom/user`.

# Configuration

The module itself has no options. However it uses the access control
mechanisms in PubSub, so users must reconfigure their microblogging node
to allow access, by setting `access_model` to `open`.
E.g. Gajim has UI for this, look for "Personal Events" → "Configure
services".