[MESOS-6561] Docker manifest fetcher fails to handle HTTP redirects

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.0.1
• Component/s: docker
• Labels: docker-fetcher
• Epic Link: Unified Container
• Assignee: Unassigned
• Reporter: Ilya
• Created: 08/Nov/16 14:59
• Updated: 11/Apr/17 19:03

Description

Internal curl() function in Docker fetcher uses curl utility with -L (follow Location) and -i (include headers) flags to fetch manifests and then parses its output (a series of raw HTTP responses). curl silently drops the body of a “redirect” response from it's output while potentially non-zero Content-Length header field is still present. This makes ResponseDecoder consume headers of a next response and fail parsing or yield incorrect results.

Right now this is not a real issue because currently Docker Registry serves image manifests without redirects.

Issue Links

• relates to: MESOS-5172 Registry puller cannot fetch blobs correctly from http Redirect 3xx urls.