Go SHP per YC

This is the extension for go-shp (https://github.com/winguse/go-shp). A open source secure HTTP proxy written in golang.

The source code can be found in https://github.com/winguse/go-shp/tree/master/extension .

This extension include features:

1. set proxy on / off for Firefox
2. rule base proxy selection
3. latency test to select proxy server

Used to intercept every outgoing network request via browser.proxy.onRequest and return a proxy routing decision. Unlike Chrome's PAC script approach, Firefox exposes a per-request JavaScript listener that returns a full proxy object — including the proxy host, port, and Proxy-Authorization header — for each request. This allows the extension to apply domain-based routing rules and embed credentials preemptively, so the proxy server never needs to issue a 407 challenge. Without this permission the extension cannot route any traffic.


Used to persist the user's configuration across browser sessions via browser.storage.local. This includes proxy host lists, routing rules, credentials, and the latency history used to rank proxy hosts by speed. Without this permission settings would be lost every time the browser is closed.


Used to schedule periodic proxy health checks via browser.alarms. The background script probes each configured proxy host at a user-defined interval (default: every minute) to measure latency and keep host rankings up to date. Without this permission the extension cannot run recurring background work reliably.


This extension is designed for self-hosted SHP (Secure HTTP Proxy) deployments. Users run their own proxy servers at arbitrary hostnames and ports — there is no fixed domain that can be listed. The <all_urls> host permission is therefore required for the following reasons:

• The proxy.onRequest listener must be registered with { urls: ['<all_urls>'] } so that every outgoing request is evaluated against the user's routing rules. A narrower URL pattern would silently skip requests and cause incorrect routing.
• The background health-check probes send requests to https://<proxy-host><authBasePath>/407 to measure latency. Since the proxy host is user-configured, no specific hostname can be declared in the manifest.

No page content is ever read or modified. The extension only observes request metadata (URL, host) to make proxy routing decisions — it never accesses response bodies or injects scripts into web pages.