Can't put cookie jar into a request #511

Activity

1. tarcieri commented on Nov 29, 2018

   

   tarcieri

   on Nov 29, 2018

   Member

   More actions

   Reusing a HTTP::CookieJar (automatically) between requests was something I had originally suggested in the form of an HTTP::Session type: #306

   It looks like you're right though, HTTP::Options#cookies does not accept an HTTP::CookieJar as an argument, and probably should.
2. odinhb commented on Sep 25, 2020

   

   odinhb

   on Sep 25, 2020

   Contributor

   More actions

   I ran into this when replacing some cURL-ing that had been done with the justification that it was easier to use cURL to maintain the session than using http.rb or other ruby http libraries. Here's the function I used:

   def cookiejar_to_hash(jar)
     hash = {}
     jar.cookies.each do |cookie|
       hash[cookie.name] = cookie.value
     end
     hash
   end

   Allowing you to

   response = HTTP.get('http://www.example.com')
   cookies = cookiejar_to_hash(response.cookies)
   new_response = HTTP.get('http://www.example.com').cookies(cookies)

   👍React with 👍2Reacted by Vucius and ilyazub
3. HoneyryderChuck commented on Sep 25, 2020

   

   HoneyryderChuck

   on Sep 25, 2020

   More actions

   @odinhb there's at least 1 http ruby library supporting it

   👍React with 👍1Reacted by ilyazub
4. tarcieri commented on Sep 25, 2020

   

   tarcieri

   on Sep 25, 2020

   Member

   More actions

   We just landed #613 which adds support for it, but it isn't released

   👍React with 👍1Reacted by Odin
5. sferik

   added

   Bug

   on Mar 11, 2026
6. sferik commented on Mar 12, 2026

   

   sferik

   on Mar 12, 2026

   Contributor

   More actions

   Chainable#cookies now accepts any enumerable of HTTP::Cookie objects in addition to a Hash, so passing a cookie jar from a previous response works directly:

   response = HTTP.get("http://example.com")
   HTTP.cookies(response.cookies).get("http://example.com/next")

   This was part of a broader cookie API refactor (0dd249f) that removed cookie management from Options and simplified Chainable#cookies to set the Cookie header directly from a Hash or Array<HTTP::Cookie>. Since HTTP::CookieJar is Enumerable and yields HTTP::Cookie objects, it should work transparently.

   Additionally, cookie jar management during redirects is now handled automatically by the Session (008c181), so manual cookie passing between redirect steps is no longer necessary.

   If you encounter any issues with the new cookie API, please reopen this issue or file a new one.
7. sferik

   closed this as completedon Mar 12, 2026
8. sferik

   added the

   Bug

   issue type on Mar 17, 2026