You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2022. It is now read-only.
When downloading or uploading a file from a protected resource and sending an authorization header (or any other headers) the native iOS code doesn't use the headers to build the request.
Both HttpDownloadFileOptions and HttpDownloadFileOptions extend HttpDownloadFileOptions which has the headers object as an optional parameter. The download/upload functions should accept the headers object like it does on Android.
The text was updated successfully, but these errors were encountered:
ynunez
added a commit
to ynunez/http
that referenced
this issue
Jan 21, 2021
Describe the bug
When downloading or uploading a file from a protected resource and sending an authorization header (or any other headers) the native iOS code doesn't use the headers to build the request.
Environments
To Reproduce
Expected behavior
Both
HttpDownloadFileOptions
andHttpDownloadFileOptions
extendHttpDownloadFileOptions
which has theheaders
object as an optional parameter. The download/upload functions should accept the headers object like it does on Android.The text was updated successfully, but these errors were encountered: