How tkohegyi/mitmjavaproxy works
Core Proxy Components
• ProxyServer (Main entry point)
• Request Interceptor System
• Response Interceptor System
• SSL/TLS Handler
• Certificate Management System
HTTP/HTTPS Processing Layer
• HTTP Client Handler
• HTTP Server Handler
• Message Processing Pipeline
• Content Encoding/Decoding System
External Interfaces
• Client Connection Point
• Server Connection Point
• Certificate Authority Interface
• [Client] <---> [MITM Proxy Server] <---> [Target Server]
Detailed Component Breakdown
• [Client]
• ↓
• [SSL/TLS Layer]
• ↓
• [Request Interceptor Chain]
• ↓
• [HTTP Processing]
• ↓
• [Response Interceptor Chain]
• ↓
• [Target Server]
• Blue: Core proxy components
• Green: Security-related components (SSL/TLS, Certificates)
• Yellow: Interceptor components
• Gray: Utility and support components
Key Relationships to Highlight:
Message Flow
• Points of interception
• Content manipulation possibilities
Security Layer
• Certificate Authority integration
• SSL/TLS handling
• Trust chain management
Interceptor Chain
• Request modification points
• Response volatility handling
• Content manipulation capabilities
Special Considerations:
Dual-nature of the proxy
• Client-facing interface
• Server-facing interface
Certificate management system
• CA certificate generation
• Certificate distribution
• Trust establishment
Features
• HTTP/HTTPS support
• Message manipulation capabilities
• Content encoding/decoding
Implementation Details to Include:
Core Classes
• ProxyServer
• RequestInterceptor
• ResponseInterceptor
• CertificateCreator
Support Systems
• ThreadPool management
• Connection handling
• Resource management
• Message flow directions
• Interception points
• Security boundaries
• Component types
• Integration points
Level of Detail:
• Keep high-level architecture visible
• Major components and their interactions
• Integration points
• Security boundaries
• Extension points for interceptors
Remember to include notes about the security implications and proper usage contexts, as emphasized in the README's warning section.