Skip to content

Only consider response code as FTP responses if FTP used#2465

Closed
agners wants to merge 1 commit intocurl:masterfrom
agners:fix-wrong-ftp-error-on-retry
Closed

Only consider response code as FTP responses if FTP used#2465
agners wants to merge 1 commit intocurl:masterfrom
agners:fix-wrong-ftp-error-on-retry

Conversation

@agners
Copy link
Contributor

@agners agners commented Apr 6, 2018

Only tread response code as FTP response codes in case the
protocol type is FTP.

This fixes an issue where an HTTP download was treated as FTP
in case libcurl returned with 33. This happens when the
download has already finished and the server responses 416:
HTTP/1.1 416 Requested Range Not Satisfiable

This should not be treated as an FTP error.

Fixes #2464

Only tread response code as FTP response codes in case the
protocol type is FTP.

This fixes an issue where an HTTP download was treated as FTP
in case libcurl returned with 33. This happens when the
download has already finished and the server responses 416:
  HTTP/1.1 416 Requested Range Not Satisfiable

This should not be treated as an FTP error.

Fixes curl#2464
@jay jay closed this in 464a019 Apr 7, 2018
@jay
Copy link
Member

jay commented Apr 7, 2018

Thanks

@lock lock bot locked as resolved and limited conversation to collaborators Jul 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Development

Successfully merging this pull request may close these issues.

FTP error when downloading file from a HTTP server with retry and continue-at arguments

2 participants