From: lain Date: Mon, 19 Aug 2019 17:00:59 +0000 (+0000) Subject: Merge branch 'develop' into 'fix/reverse-proxy-body-too-large' X-Git-Url: https://git.squeep.com/?a=commitdiff_plain;h=d2c9befc64d4b8d4f56b5e23afeb1b720767e7ff;p=akkoma Merge branch 'develop' into 'fix/reverse-proxy-body-too-large' # Conflicts: # CHANGELOG.md --- d2c9befc64d4b8d4f56b5e23afeb1b720767e7ff diff --cc CHANGELOG.md index d47e98cd4,fa7818137..90d10fdbc --- a/CHANGELOG.md +++ b/CHANGELOG.md @@@ -42,9 -43,10 +43,11 @@@ The format is based on [Keep a Changelo - Pleroma.Upload base_url was not automatically whitelisted by MediaProxy. Now your custom CDN or file hosting will be accessed directly as expected. - Report email not being sent to admins when the reporter is a remote user - MRF: ensure that subdomain_match calls are case-insensitive +- Reverse Proxy limiting `max_body_length` was incorrectly defined and only checked `Content-Length` headers which may not be sufficient in some circumstances + - MRF: fix use of unserializable keyword lists in describe() implementations ### Added + - Conversations: Add Pleroma-specific conversation endpoints and status posting extensions. Run the `bump_all_conversations` task again to create the necessary data. - **Breaking:** MRF describe API, which adds support for exposing configuration information about MRF policies to NodeInfo. Custom modules will need to be updated by adding, at the very least, `def describe, do: {:ok, %{}}` to the MRF policy modules. - MRF: Support for priming the mediaproxy cache (`Pleroma.Web.ActivityPub.MRF.MediaProxyWarmingPolicy`)