txtdot
Self-HostedOpen-source HTTP proxy for logging and inspecting network traffic
Overview
txtdot is a lightweight, self-hosted HTTP proxy built for debugging and testing. It captures full HTTP/HTTPS request-response details (headers, body, status codes) and displays them in an intuitive web interface. Deployable via a single Docker command with no extra dependencies, it auto-generates self-signed certificates for HTTPS traffic. Ideal for local development, it lets developers inspect client-server interactions without relying on third-party tools. Open-source under the MIT License, it’s customizable to fit specific workflow needs.
Self-Hosting Resources
Below is a reference structure for docker-compose.yml.
⚠️ Do NOT run blindly. Replace placeholders with official values.
version: '3'
services:
txtdot:
image: <OFFICIAL_IMAGE_NAME>:latest
container_name: txtdot
ports:
- "8080:<APP_INTERNAL_PORT>"
volumes:
- ./data:/app/data
restart: unless-stopped Key Features
- Capture HTTP/HTTPS traffic with full details
- Clean web UI for inspecting logs
- One-command Docker deployment
- Auto-generated self-signed HTTPS certificates
Frequently Asked Questions
? Is txtdot hard to install?
No—txtdot deploys via a single Docker command. Pull the image, run the container, and it starts the proxy and web UI immediately. HTTPS support uses auto-generated self-signed certificates, which you can trust in your local environment for testing.
? Is it a good alternative to Charles Proxy?
Yes, for developers seeking a free, self-hosted alternative. While it misses advanced features like breakpoints, txtdot excels at basic traffic logging and inspection with a simple interface. It eliminates subscription costs for local debugging needs.
? Is txtdot completely free?
Yes—txtdot is open-source under the MIT License. There are no paid tiers, hidden fees, or usage restrictions. You can self-host, modify, and distribute it freely.
Top Alternatives
People Also Ask about txtdot
Tool Info
Pros
- ⊕ Lightweight and resource-efficient
- ⊕ Zero complex configuration required
- ⊕ Open-source and fully customizable
- ⊕ No subscription or hidden costs
Cons
- ⊖ Lacks advanced features like breakpoints or throttling
- ⊖ Self-signed certificates need manual trust setup
- ⊖ Not designed for production proxy use cases