Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Serve PAC file to selectively proxy only watched hosts

未关闭
#1,531 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
csharp

调研方向

首先检查现有的 API controller 以及切换系统代理设置的代码。跟踪 urlsToWatch 的配置方式,然后确定如何接入 /proxy.pac endpoint 和平台特定的自动配置。完成的标准是:受监视的主机通过代理路由,其他流量返回 DIRECT,并且 endpoint 提供所需的 PAC MIME 类型。

由索引模型根据 Issue 内容生成。

描述

Currently, when Dev Proxy runs as a system proxy, all HTTP/HTTPS traffic flows through it. Dev Proxy filters requests internally based on urlsToWatch, but unrelated traffic still takes the detour through the proxy. This can cause issues with services that are sensitive to proxying (e.g., Azure Functions startup, Teams auth) and adds unnecessary latency to non-watched traffic.

Proposal: Have Dev Proxy serve a PAC (Proxy Auto-Config) file that routes only watched hosts through the proxy. All other traffic goes direct.

How it would work:

  1. Dev Proxy generates a FindProxyForURL() script from the configured urlsToWatch hosts
  2. Serves it at an endpoint like http://127.0.0.1:{port}/proxy.pac with MIME type application/x-ns-proxy-autoconfig
  3. Instead of setting the system HTTP/HTTPS proxy, sets the system's auto-config URL to point to this PAC file
    • macOS: networksetup -setautoproxyurl <service> http://127.0.0.1:{port}/proxy.pac
    • Windows: set AutoConfigURL registry key or use the proxy library equivalent

Example generated PAC file for urlsToWatch: ["https://graph.microsoft.com/*", "https://api.contoso.com/*"]:

function FindProxyForURL(url, host) {
  if (shExpMatch(host, "graph.microsoft.com") ||
      shExpMatch(host, "api.contoso.com")) {
    return "PROXY 127.0.0.1:8000";
  }
  return "DIRECT";
}

Limitations:

  • PAC files operate at the host level, not URL-path level. Fine-grained URL matching still happens inside the proxy as it does today.
  • Linux doesn't have a standard system-wide auto-config URL mechanism (same limitation as the current system proxy setup).

Benefits:

  • Non-watched traffic never touches the proxy — faster, fewer side effects
  • Could resolve issues with Azure Functions, Teams auth, and other services that break when proxied
  • Minimal implementation surface — Dev Proxy already has an API controller and already toggles system proxy settings

Derived from https://github.com/dotnet/dev-proxy/issues/1368.

主要语言
C#
星标
833
派生
90
平均合并
18 小时 41 分钟
30 天内合并 PR
45

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

dotnet/dev-proxy 的其他 Issue

查看 dotnet/dev-proxy 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。