mitmproxy / mitmproxy/mitmproxy
Response always 400 by refusing connect Upstream server
Open
Nobody has claimed this yet.
kind/triage
- Dominant language
- Python
- Stars
- 45.1k
- Forks
- 4.7k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 16
Description
Problem Description
What is the difference between mitmproxy 6.0.2 and 7.0.0
I try to connect my proxy with mitmproxy as below:
mitmproxy -m upstream:http://<this is my proxy server>:9782 --ssl-insecure
And i can get the correct response in terminal tool when i use mitmproxy 6.0.2
Steps to reproduce the behavior:
- Upgrade 6.0.2 to 7.0.0
- Connect mitmproxy as
mitmproxy -m upstream:http://<this is my proxy server>:9782 --ssl-insecure - View api response in terminal tool
- The response always 400
System Information
Mitmproxy: 7.0.0
Python: 3.10.0
OpenSSL: OpenSSL 1.1.1i 8 Dec 2020
Platform: macOS-12.6.7-x86_64-i386-64bit
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported command in mitmproxy 7.0.0 and compare its behavior with 6.0.2 using the same upstream proxy. Trace where the upstream connection produces the 400 response; done means identifying the regression, restoring the expected API response, and verifying the reproduction steps no longer fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100