client.api() throws "Unable to parse the URL" for relative paths containing https:// in the query

未关闭 适合新手
#2,039 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@pcbeingused333 已经在做这个了。

开始于 2026年11月16日。

  • #2040 来自 @pcbeingused333 —— 未关闭

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
85/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
领域
api

调研方向

从 parsePath 开始,它位于 src/GraphRequest.ts 第 134 行附近,绝对 URL 检查使用 path.indexOf("https://"),然后才调用 new URL(path);针对本地构建运行 issue 中的复现脚本,以看到这三个失败。将测试改为不区分大小写的 startsWith 检查,使只有真正的绝对路径进入该分支,并保持相对分支根据配置的基础 URL 加版本进行解析。完成后的样子是:三个复现路径都打印出预期的 https://graph.microsoft.com/v1.0/... URL,而完整的 https://graph.microsoft.com/... 路径仍然可以解析,并且在现有的 GraphRequest 测试套件中有一个回归测试。

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

描述

Describe the bug

client.api(path) throws Error: Unable to parse the URL: ... (GraphClientError) when given a relative path whose query string or OData function parameter contains https://, such as /sites?search=https://contoso.sharepoint.com or /me/events?$filter=onlineMeeting/joinUrl eq 'https://...'.

In 3.0.7, the same calls did not throw, but stripped https:// from the query and built a broken URL (https:/v1.0/sites?search=contoso.sharepoint.com).

Expected behavior

Relative paths should resolve against the configured base URL and version (https://graph.microsoft.com/v1.0/sites?search=https://contoso.sharepoint.com, etc.), matching the behavior of .query() and .filter() for the same values.

How to reproduce
npm install @microsoft/[email protected]
node repro.js

repro.js:

const { Client } = require("@microsoft/microsoft-graph-client");
const client = Client.init({ authProvider: (done) => done(null, "token") });

for (const path of [
  "/sites?search=https://contoso.sharepoint.com",
  "/me/events?$filter=onlineMeeting/joinUrl eq 'https://teams.microsoft.com/l/x'",
  "/me/drive/root/search(q='https://example')",
]) {
  try {
    console.log(client.api(path).buildFullUrl());
  } catch (e) {
    console.log(e.message);
  }
}

Actual output (3.1.0):

Unable to parse the URL: /sites?search=https://contoso.sharepoint.com
Unable to parse the URL: /me/events?$filter=onlineMeeting/joinUrl eq 'https://teams.microsoft.com/l/x'
Unable to parse the URL: /me/drive/root/search(q='https://example')
SDK Version

3.1.0 (also on dev 4434ef722 and main ba4103712)

Latest version known to work for scenario above?

None (3.0.7 returned malformed URLs such as https:/v1.0/sites?search=contoso.sharepoint.com instead of throwing)

Known Workarounds

Pass the parameter through .query() / .filter() instead of inline in api(), or percent-encode :// in the parameter value.

Debug output
Click to expand log
Error: Unable to parse the URL: /sites?search=https://contoso.sharepoint.com
    at new GraphClientError (node_modules/@microsoft/microsoft-graph-client/lib/src/GraphClientError.js:30:28)
    at GraphRequest.parsePath (node_modules/@microsoft/microsoft-graph-client/lib/src/GraphRequest.js:51:27)
    at new GraphRequest (node_modules/@microsoft/microsoft-graph-client/lib/src/GraphRequest.js:105:14)
    at Client.api (node_modules/@microsoft/microsoft-graph-client/lib/src/Client.js:97:16)
Configuration
  • OS: Linux x64
  • Node.js: v26.13.0 (not OS- or runtime-specific)
Other information

GraphRequest.parsePath (src/GraphRequest.ts, line 134) checks if (path.indexOf("https://") !== -1) to decide whether path is an absolute URL, and PR #2000 added new URL(path) inside that branch. Checking whether path starts with https:// (case-insensitively) instead of indexOf would avoid treating query values containing https:// as absolute URLs.

Credit: https://ucsbplse.github.io/

主要语言
TypeScript
星标
836
派生
241
平均合并
1 天 12 小时
30 天内合并 PR
10

环境准备

从这里开始

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

microsoftgraph/msgraph-sdk-javascript 的其他 Issue

查看 microsoftgraph/msgraph-sdk-javascript 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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