summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMark Felder <feld@feld.me>2023-12-28 23:09:33 -0500
committerMark Felder <feld@feld.me>2023-12-28 23:09:33 -0500
commitaa070c7dafbceb33b9656f54aa552672497942f6 (patch)
treeff795e712835dbc2ace68af45160c1a2d47e8ed0
parenta6fd251e440ec3c6734f6b084c8a69f442bcebb0 (diff)
downloadpleroma-aa070c7dafbceb33b9656f54aa552672497942f6.tar.gz
pleroma-aa070c7dafbceb33b9656f54aa552672497942f6.zip
Handle 401s as I have observed it in the wild
-rw-r--r--changelog.d/handle_object_fetch_failures.change2
-rw-r--r--lib/pleroma/object/fetcher.ex2
2 files changed, 2 insertions, 2 deletions
diff --git a/changelog.d/handle_object_fetch_failures.change b/changelog.d/handle_object_fetch_failures.change
index e115c8012..ae44e6f4b 100644
--- a/changelog.d/handle_object_fetch_failures.change
+++ b/changelog.d/handle_object_fetch_failures.change
@@ -1 +1 @@
-Remote object fetch failures will prevent the object fetch job from retrying if the object request returns 403, 404, 410, or exceeds the maximum thread depth.
+Remote object fetch failures will prevent the object fetch job from retrying if the object request returns 401, 403, 404, 410, or exceeds the maximum thread depth.
diff --git a/lib/pleroma/object/fetcher.ex b/lib/pleroma/object/fetcher.ex
index 972dfaf28..af5642af4 100644
--- a/lib/pleroma/object/fetcher.ex
+++ b/lib/pleroma/object/fetcher.ex
@@ -219,7 +219,7 @@ defmodule Pleroma.Object.Fetcher do
{:error, {:content_type, nil}}
end
- {:ok, %{status: 403}} ->
+ {:ok, %{status: code}} when code in [401, 403] ->
{:error, :forbidden}
{:ok, %{status: code}} when code in [404, 410] ->