Handle 401s as I have observed it in the wild
This commit is contained in:
parent
a6fd251e44
commit
aa070c7daf
|
@ -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.
|
||||||
|
|
|
@ -219,7 +219,7 @@ defp get_object(id) do
|
||||||
{:error, {:content_type, nil}}
|
{:error, {:content_type, nil}}
|
||||||
end
|
end
|
||||||
|
|
||||||
{:ok, %{status: 403}} ->
|
{:ok, %{status: code}} when code in [401, 403] ->
|
||||||
{:error, :forbidden}
|
{:error, :forbidden}
|
||||||
|
|
||||||
{:ok, %{status: code}} when code in [404, 410] ->
|
{:ok, %{status: code}} when code in [404, 410] ->
|
||||||
|
|
Loading…
Reference in New Issue