Increase the :max_body for Rich Media to 5MB

Websites are increasingly getting more bloated with tricks like inlining content (e.g., CNN.com) which puts pages at or above 5MB. This value may still be too low.
This commit is contained in:
Mark Felder 2024-02-11 16:53:21 -05:00 committed by Floatingghost
parent 5da9cbd8a5
commit bfe4152385
3 changed files with 6 additions and 4 deletions

View file

@ -440,8 +440,9 @@ config :pleroma, :rich_media,
Pleroma.Web.RichMedia.Parsers.TwitterCard,
Pleroma.Web.RichMedia.Parsers.OEmbed
],
failure_backoff: :timer.minutes(20),
ttl_setters: [Pleroma.Web.RichMedia.Parser.TTL.AwsSignedUrl]
ttl_setters: [Pleroma.Web.RichMedia.Parser.TTL.AwsSignedUrl],
failure_backoff: 60_000,
max_body: 5_000_000
config :pleroma, :media_proxy,
enabled: false,

View file

@ -63,7 +63,8 @@ config :tesla, adapter: Tesla.Mock
config :pleroma, :rich_media,
enabled: false,
ignore_hosts: [],
ignore_tld: ["local", "localdomain", "lan"]
ignore_tld: ["local", "localdomain", "lan"],
max_body: 2_000_000
config :pleroma, :instance,
multi_factor_authentication: [

View file

@ -59,7 +59,7 @@ defmodule Pleroma.Web.RichMedia.Helpers do
defp http_options() do
[
pool: :media,
max_body: Config.get([:rich_media, :max_body], 2_000_000)
max_body: Config.get([:rich_media, :max_body], 5_000_000)
]
end
end