Skip to content
This repository was archived by the owner on Jun 11, 2024. It is now read-only.
This repository was archived by the owner on Jun 11, 2024. It is now read-only.

How to migrate to mitmproxy #395

Open
@dkbarn

Description

@dkbarn

The README states that this project is deprecated and mitmproxy is intended to be the replacement. But after reading through the documentation for mitmproxy it is unclear to me how to migrate from browserup-proxy to it, because it seems to operate in a fundamentally different way.

Are there any guides or tutorials available to help users of browserup-proxy migrate to mitmproxy?

With browserup-proxy you are running a persistent proxy server in the background, and the API allows you to "attach" to that running process, enabling you to begin and end sessions and capture traffic from a separate process.

In contrast, mitmproxy does not operate with this same client/server model. There is only the running instance of the proxy server, but no way to "attach" to that running process from your own application. Instead the Python API can only hook into events in the same process, and thus any Python addons must be passed as arguments to the mitmproxy command itself. So it is unclear to me how someone is expected to accomplish the same functionality as browserup-proxy using mitmproxy.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions