Sorry, I don't think I'm following. What would the meaning of the value returned from checkRedirect be?<div><br></div><div>--Myles<br><br><div class="gmail_quote">On Tue, Jan 24, 2012 at 10:47 AM, Michael Snoyman <span dir="ltr"><<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Jan 24, 2012 at 6:57 PM, Myles C. Maxfield<br>
<div class="im"><<a href="mailto:myles.maxfield@gmail.com">myles.maxfield@gmail.com</a>> wrote:<br>
><br>
> On Mon, Jan 23, 2012 at 10:43 PM, Michael Snoyman <<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>><br>
> wrote:<br>
>><br>
>> On Tue, Jan 24, 2012 at 8:37 AM, Myles C. Maxfield<br>
>> <<a href="mailto:myles.maxfield@gmail.com">myles.maxfield@gmail.com</a>> wrote:<br>
>> > I have attached a patch to add a redirect chain to the Response<br>
>> > datatype.<br>
>> > Comments on this patch are very welcome.<br>
>><br>
>> I thought that this isn't necessary since a client wanting to track<br>
>> all the redirects could just handle them manually by setting the<br>
>> redirect count to 0.<br>
><br>
> It seems like a lot of work to re-implement the redirection-following code,<br>
> just to know which URL the bytes are coming from. I feel that adding this<br>
> field makes the library easier to use, but it's your call.<br>
<br>
</div>If that's the concern, I'd much rather just expose a function to help<br>
with dealing with redirects, rather than sticking a rather arbitrary<br>
[Ascii] in everyone's Response. I think a function along the lines of:<br>
<br>
checkRedirect :: Response -> Maybe Request<br>
<br>
would fit the bill, and could be extracted from the current `http` function.<br>
<span class="HOEnZb"><font color="#888888"><br>
Michael<br>
</font></span></blockquote></div><br></div>