FollowRedirectsAttribute messes up some response headers

If FollowRedirectsAttribute is set to true, some reply response headers contains both headers of original request and redirected one.

For example content-type may have something like  "text/html; charset=iso-8859-1, image/png", what is basically nonsense. Some other headers have duplicated the same values. And some like Content-Length is taken only from redirected request regardles of  presence in both requests.

In other words it's full of clutter.

There is a dump here for example

[0] "accept-ranges" "bytes"

[1] "connection" "keep-alive, keep-alive"

[2] "content-length" "1828"

[3] "content-type" "text/html; charset=iso-8859-1, image/png"

[4] "date" "Wed, 07 Jun 2017 19:06:04 GMT, Wed, 07 Jun 2017 19:06:04 GMT"

[5] "etag" ""724-5515a6da52800""

[6] "last-modified" "Wed, 07 Jun 2017 08:21:52 GMT"

[7] "location" "http://pix.academ.info/images/img/2017/06/07/9ad27447c2c693ef5a657d7b53e462d6.png"

[8] "server" "nginx/1.10.3, nginx/1.10.3"

[9] "strict-transport-security" "max-age=15768000, max-age=15768000"