Skip to content

HTTP::Session #306

Closed
Closed

Description

@tarcieri

Many other HTTP libraries provide a session abstraction as a way of carrying state (i.e. cookies) between requests, potentially across different origins (e.g. following redirects).

http://docs.python-requests.org/en/master/user/advanced/#session-objects

I think this is the best way to solve #302 (cc @zanker)

Activity

  1. added this to the v2.0 milestone on Mar 20, 2016
  2. modified the milestones: v2.0, on May 5, 2016
  3. removed this from the v2.2 milestone on Oct 14, 2018
  4. janko commented on Nov 18, 2018

    @janko
    Member

    I that the session objects might allow us to make HTTP::Client thread-safe (see socketry/async-io#17). Currently I would not expect that HTTP::Client caches the @connection object without looking at it; and I still assumed that it's not, even though I'm very familiar with http.rb codebase by now. But with session objects it would be obvious that the HTTP::Client is (hopefully) immutable, while HTTP::Session uses the same connection.

  5. added this to the v5.0.0 milestone on Mar 11, 2019
  6. modified the milestones: v5.0.0, v6.0.0 on Jun 30, 2025
  7. added theissue type on Mar 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions