Project

Profile

Help

Task #6870

closed

Document for plugin writers the usefullness of mitmproxy

Added by bmbouter almost 4 years ago. Updated about 2 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation
Sprint:
Quarter:

Description

Ticket moved to GitHub: "pulp/pulpcore/1900":https://github.com/pulp/pulpcore/issues/1900


Background

The mitmproxy are extremely useful for debugging how services work which normally talk using TLS. Say you want to debug a CLI talking to it's server so that you can reverse engineer how Pulp needs to behave as either the client or server. For example debugging between the ansible-galaxy CLI and galaxy.ansible.com (the server side). You could use mitmproxy in the middle like:

ansible-galaxy CLI <--> mitmproxy <--> ansible.galaxy.com.

You can enable this easily if the CLI has any sort of "proxy config".

Example

Setup mitmproxy and run it

pip install mitmproxy
mitmweb -v -v -v --listen-port 8088 --web-port 8089 -k

Configure the CLI to talk "through" mitmproxy and to ignore that it doesn't have a trusted cert

export ANSIBLE_GALAXY_IGNORE=true export ANSIBLE_CONFIG=/home/vagrant/devel/automation_hub.cfg export HTTPS_PROXY=localhost:8088

Usage

Make CLI requests and read all requests and responses from the mitmproxy UI.

Actions #1

Updated by pulpbot about 2 years ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF