microsoftgraph / microsoftgraph/msgraph-sdk-java

Site `search` query parameter is inconsistent between SDK and Graph Explorer

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

还没有人认领这个 Issue。

status:waiting-for-triage type:bug
主要语言
Java
星标
444
派生
154
平均合并
18 小时 28 分钟
30 天内合并 PR
4

描述

Describe the bug

When using Graph Explorer, the API endpoint https://graph.microsoft.com/v1.0/sites returns nothing.

With Graph Explorer, it appears that using ?search=* works to return all sites.

When using the SDK, the same endpoint returns sites, and specifying queryParameters.search = "*" throws:

Syntax error: character '*' is not valid at position 0 in '*'.
com.microsoft.graph.models.odataerrors.ODataError: Syntax error: character '*' is not valid at position 0 in '*'.

based on the response:

{
  "error": {
    "code": "BadRequest",
    "message": "Syntax error: character '*' is not valid at position 0 in '*'.",
    "innerError": {
      "date": "2025-03-31T18:56:12",
      "request-id": "f29db1f9-b0d7-4d4b-a724-7599a932bcca",
      "client-request-id": "fb1f170c-a4c0-4eb6-bb8c-852e3d3c7762"
    }
  }
}

These inconsistencies (along with issues like #2344 and #2345 ) make it very difficult to sanely develop applications using the MS Graph SDK.

One difference is that I am using client cert / secret credentials for the SDK and personal credentials for Explorer. That should not affect the API's functional behavior though.

Expected behavior

APIs should have consistent behavior.

How to reproduce

See above.

SDK Version

6.33.0

Latest version known to work for scenario above?

No response

Known Workarounds

Pull out hair, write code with many "argh" comments, and proceed

Debug output

No response

Configuration

No response

Other information

No response

贡献指南

打开贡献指南

从这里开始

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

调研方向

首先在 Graph Explorer 中以及使用 SDK 版本 6.33.0 重现 /v1.0/sites 请求,同时比较凭据和序列化后的搜索查询。追踪差异是在 Java SDK 请求中,还是在 Graph API 的行为中;当确定了负责的组件,并确立了一致的行为或记录在案的限制时,即表示完成。

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

评估

技术栈
java
领域
api
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

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