I have attached a patch to add a redirect chain to the Response datatype. Comments on this patch are very welcome.<div><br></div><div>I was originally going to include the entire Request object in the redirection chain, but Request objects are parameterized with a type &#39;m&#39;, so including a &#39;Request m&#39; field would force the Response type to be parameterized as well. I felt that would be too large a change, so I made the type of the redirection chain W.Ascii.</div>

<div><br></div><div>Perhaps its worth using the &#39;forall&#39; keyword to get rid of the pesky &#39;m&#39; type parameter for Requests?</div><div><br></div><div><div>data RequestBody</div><div>    = RequestBodyLBS L.ByteString</div>

<div>    | RequestBodyBS S.ByteString</div><div>    | RequestBodyBuilder Int64 Blaze.Builder</div><div>    | forall m. RequestBodySource Int64 (C.Source m Blaze.Builder)</div><div>    | forall m. RequestBodySourceChunked (C.Source m Blaze.Builder)</div>

</div><div><br></div><div>--Myles<br><br><div class="gmail_quote">On Mon, Jan 23, 2012 at 3:31 AM, Michael Snoyman <span dir="ltr">&lt;<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div class="im">On Mon, Jan 23, 2012 at 1:20 PM, Aristid Breitkreuz<br>
&lt;<a href="mailto:aristidb@googlemail.com">aristidb@googlemail.com</a>&gt; wrote:<br>
&gt; Rejecting cookies is not without precedent.<br>
&gt;<br>
&gt; If you must force cookie handling upon us, at least make it possible to<br>
&gt; selectively reject them.<br>
&gt;<br>
&gt; Aristid<br>
<br>
</div>If you turn off automatic redirects, then you won&#39;t have cookie<br>
handling. I&#39;d be interested to hear of a use case where you would want<br>
to avoid passing cookies after a redirect.<br>
<span class="HOEnZb"><font color="#888888"><br>
Michael<br>
</font></span></blockquote></div><br></div>