Skip to content

fix: route plain HTTP proxy requests direct in google_only mode#256

Merged
therealaleph merged 1 commit intotherealaleph:mainfrom
dazzling-no-more:fix/google-only-http
Apr 26, 2026
Merged

fix: route plain HTTP proxy requests direct in google_only mode#256
therealaleph merged 1 commit intotherealaleph:mainfrom
dazzling-no-more:fix/google-only-http

Conversation

@dazzling-no-more
Copy link
Copy Markdown
Contributor

In google_only bootstrap mode, plain HTTP proxy requests (GET http://example.com/) returned a 502 even though the equivalent HTTPS via CONNECT already fell through to direct TCP. Typing http://... in the address bar produced "google_only mode: plain HTTP proxy requests are not supported."

@therealaleph therealaleph merged commit 75bec21 into therealaleph:main Apr 26, 2026
@dazzling-no-more dazzling-no-more deleted the fix/google-only-http branch April 26, 2026 13:55
therealaleph added a commit that referenced this pull request Apr 26, 2026
- #245 (@Parsa307): match twitter.com in X.com URL normalization
- #255 (@dazzling-no-more): copy-logs button + selectable log lines on Android
- #257 (@dazzling-no-more): bulk paste of multiple deployment IDs on Android
- #256 (@dazzling-no-more): plain HTTP proxy passthrough in google_only mode
  (used to return 502; now falls through to direct TCP / upstream_socks5,
  matching the existing CONNECT behavior)

No protocol or wire-format changes; existing config and Apps Script
deployments work unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants