You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: enable Squid intercept mode for NAT-redirected traffic (#520)
* fix: enable Squid intercept mode for NAT-redirected traffic
When traffic is NAT'd (DNAT) to Squid proxy, clients send relative URLs
(GET /path) because they don't know they're talking to a proxy. Squid's
normal proxy mode requires absolute URLs (GET http://example.com/path),
causing "Invalid URL - Missing hostname" errors.
This fix:
- Adds interceptPort to SquidConfig for transparent proxy traffic
- Configures Squid with `http_port 3129 intercept` for NAT'd traffic
- Updates iptables rules to redirect to intercept port (3129) not
regular port (3128)
- Keeps regular port (3128) for explicit proxy usage via HTTP_PROXY
This fixes Codex/rmcp OAuth discovery timeouts - requests now reach
the MCP gateway instead of being blocked by Squid.
Fixes#519
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* fix: add intercept port to SSL Bump mode and update healthcheck
1. Add intercept port (3129) to SSL Bump section: When SSL Bump was
enabled, the generateSslBumpSection() function generated its own
port config but did not include the intercept port needed for
NAT-redirected transparent proxy traffic.
2. Update healthcheck to verify both ports: The Docker healthcheck
only verified port 3128, not ensuring port 3129 was also working.
Now checks both ports to ensure complete Squid proxy functionality.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
0 commit comments