Working with cookies (question) about req HOT 8 OPEN

I am unsure what you are asking. Req allows you to use a specific CookieJar and then get it from the response. For all the manipulations you should use the functions from http-client (which I believe are pure). Would you like Req to provide a more declarative API for cookie manipulation?

In any other language (even F#) I could do this from scratch (with zero previous knowledge) maybe for 20 minutes just copy-pasting from Stackoverflow.

It hurts my heart to discover that Haskell sucks so badly even at simplest tasks. I do not understand why people use it for anything, honestly.

from req.

Default route is obvious.

1. Google search "Haskell https", req is second link.
2. Open req.
3. Searching for cookies (I have them already). OOPS.

I understand that the main point of your library was completely different. But now it's in the wild and faced people with almost zero Haskell knowledge.

from req.

I wish to use cookies across requests. I am aware that a CookieJar can be obtained from a response. But to merge cookies across requests, I need updateCookieJar from Network.HTTP.Client. updateCookieJar requires a Request parameter, which isn't exposed by req. It would be very helpful if req could expose the underlying Request. Thanks.

from req.

To give a real world example: I was confronted by the need to emulate a browser state, and I ended up threading an MVar through, like this:

jar <- newMVar (mempty @CookieJar)
…
post jar … >>= \ response -> do …
…
where
  post :: MVar CookieJar -> Url 'Http -> ByteString -> IO BsResponse
  post cookieJarMVar url body = modifyMVar cookieJarMVar \ jar -> do
    response <- runReq httpConfig $ req POST url (ReqBodyBs body) (Proxy @BsResponse) (cookieJar jar)
    return (responseCookieJar response, response)

I wrapped all the methods I need like this. It works fine.

I am not sure if this package needs to incorporate this feature, but it seems to be a common use case and rolling out the wrappers takes some typing. @mrkkrp you are in the best position to judge if the code to this end should be admitted to the library, but surely at least some examples and directions may be given.

from req.

@kindaro: Thanks. Yes, I am able to reuse the cookies returned in one response for the following request. The above is sufficient If all responses contained 'set-cookie' values for the same set of cookies. But if different responses update subsets of the cookie-jar, then cookies need to be accumulated across requests. In the case, one would need to use updateCookieJar, which requires a Request object. Unfortunately, req does not expose the underlying Request.

from req.

Oh I see, so you have some requests that do not send back a cookie jar. At first I did not realize that.

It looks like some sort of a monad here, a hybrid between Writer and State.

from req.

Am I correct that we could solve (or at least alleviate) the issue by adding a new method to the HttpResponse type class which would allow us to get the Request used to obtain the response?

from req.

I think you can extract the cookieJar from response after the request and put it into a State monad. You can merge multi cookieJar across requests by getting the previous one and <> the current one because cookieJar is the instance of monoid if I remember correctly.

from req.