Skip to content

Why not synchronize the request header between selenium and requests ? #37

Closed

Description

@IversionBY

I found that the request header is not synchronization when I used 's.headers.update' to update a header,and there is a question that s.get() method works well,but the s.driver.get() method does not work satisfyingly!The header is not synchronization.Maybe they could work synchronously one day!

Activity

  1. changed the title [-]why not synchronize the request header between selenium and requests ?[/-] [+]Why not synchronize the request header between selenium and requests ?[/+] on Apr 14, 2018
  2. lordjabez commented on Oct 1, 2026

    @lordjabez
    Collaborator

    Partly addressed in #221 (0.6.0). A custom User-Agent on the session is now passed to Requestium's own Chrome at launch. transfer_driver_cookies_to_session() already copies the browser's user agent the other way. Syncing all headers is deliberately not done, because Chrome only takes headers at launch through flags and would end up overriding its own Accept, Accept-Language and similar headers. Closing this; open a new issue if there's a specific header you need.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions