Authorization header added only if first request returns 401

App version: 3.7.0

Expected behaviour:
Authorization header always included when credentials defined

Current behaviour:
Authorization header included as a fallback for 401 response from the 1st request (two HTP request fired)

Steps to reproduce:

  1. Define RSS feed with authorization enabled (login, passowrd)
  2. Add credentials
  3. Refresh feed

This isn’t really a serious bug but I think current approach is not optimal and make the app to work a bit slower due to redundant requests.

Is there any reason to have the current approach instead of simply adding Authorization if defined always thus reducing two requests into single one?

Hi, the current approach is used because downloads from Amazon S3 failed when sending the header. See Prevent authentication header to be set for s3 presigned-urls by eirikv · Pull Request #2087 · AntennaPod/AntennaPod · GitHub

1 Like