Even if the server returns a 401 (in my test scenario), the download is returned as completed and finished. The response body is then saved in the file given as the target file from options. This is a wrong behaviour in my mind.
I think this misbehaviour is coming from the underlying fancy-downloader library.
Even if the server returns a 401 (in my test scenario), the download is returned as completed and finished. The response body is then saved in the file given as the target file from options. This is a wrong behaviour in my mind.
I think this misbehaviour is coming from the underlying fancy-downloader library.
Which platform(s) does your issue occur on?