To: <span style="font-family:sans-serif;font-size:13px;line-height:18px;text-align:left;background-color:rgb(255,255,255)">Michael Snoyman, author and maintainer of http-conduit</span><div>CC: haskell-cafe</div><div><br></div>

<div>Hello!<div><br></div><div>I am interested in contributing to the http-conduit library. I&#39;ve been using it for a little while and reading through its source, but have felt that it could be improved with two features:</div>


<div><ul><li>Allowing the caller to know the final URL that ultimately resulted in the HTTP Source. Because httpRaw is not exported, the caller can&#39;t even re-implement the redirect-following code themselves. Ideally, the caller would be able to know not only the final URL, but also the entire chain of URLs that led to the final request. I was thinking that it would be even cooler if the caller could be notified of these redirects as they happen in another thread. There are a couple ways to implement this that I have been thinking about:</li>


<ul><li>A straightforward way would be to add a [W.Ascii] to the type of Response, and getResponse can fill in this extra field. getResponse already knows about the Request so it can tell if the response should be gunzipped.</li>

<li>It would be nice for the caller to be able to know in real time what URLs the request is being redirected to. A possible way to do this would be for the &#39;http&#39; function to take an extra argument of type (Maybe (Control.Concurrent.Chan W.Ascii)) which httpRaw can push URLs into. If the caller doesn&#39;t want to use this variable, they can simply pass Nothing. Otherwise, the caller can create an IO thread which reads the Chan until some termination condition is met (Perhaps this will change the type of the extra argument to (Maybe (Chan (Maybe W.Ascii)))). I like this solution, though I can see how it could be considered too heavyweight.</li>

</ul><li>Making the redirection aware of cookies. There are redirects around the web where the first URL returns a Set-Cookie header and a 3xx code which redirects to another site that expects the cookie that the first HTTP transaction set. I propose to add an (IORef to a Data.Set of Cookies) to the Manager datatype, letting the Manager act as a cookie store as well as a repository of available TCP connections. httpRaw could deal with the cookie store. Network.HTTP.Types does not declare a Cookie datatype, so I would probably be adding one. I would probably take it directly from Network.HTTP.Cookie.</li>

</ul>I&#39;d be happy to do both of these things, but I&#39;m hoping for your input on how to go about this endeavor. Are these features even good to be pursuing? Should I be going about this entirely differently?</div><div>

<br></div><div>Thanks,</div><div>Myles C. Maxfield</div><div><br></div><div>P.S. I&#39;m curious about the lack of Network.URI throughout Network.HTTP.Conduit. Is there a particular design decision that led you to use raw ascii strings?</div>


</div>