HTTPoison.get! follow_redirect does not work with an async request

Nobody has claimed this yet.

I'm writing a streaming processor for some large files in a Hadoop cluster. The files are too big to keep in memory, so I want to use async get! requests into a Stream.resource. The Hadoop cluster will provide a redirect from the name node to the cluster node with the file actually on it. However, follow_redirect doesn't seem to work with an async request.

If I do an async request without follow_redirect, I get back a %HTTPoison.AsyncStatus, %HTTPoison.AsyncHeaders and %HTTPoison.AsyncEnd messages showing the 307 status along with the redirect "Location" in the headers.

If I do an async request with follow_redirect, I only get a %HTTPoison.AsyncRedirect. There is no %HTTPoison.AsyncStatus message with a 307, or a %HTTPoison.AsyncEnd, only the redirect. There are no other messages in the mailbox, and the request doesn't follow the redirect even though it's a GET, and the status is 307.

No source files or tests are named. Reproduce an asynchronous GET with follow_redirect against a 307 response, then trace the AsyncRedirect handling and compare it with the messages from a request without redirects. Done means the redirect is followed and the expected asynchronous response messages are delivered.

Written by the indexing model from the issue text.