Headers are sometimes not being set correctly with New Outlook for Windows

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

还没有人认领这个 Issue。

评估

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

调研方向

Start by reproducing the consecutive axios.patch calls and the subsequent Microsoft Graph send through New Outlook for Windows, comparing them with the browser version. Check whether the first singleValueExtendedProperty is missing after the sequence; done means establishing a reproducible result and whether the behavior belongs to the SDK, Microsoft Graph, or Outlook.

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

描述

Our application is an add-in developed in react (typescript) and makes use of the microsoft graph apis to do certain actions.

Our add-in sets three headers (via patch with microsoft graph api) consecutively on a draft email and then sends it (via microsoft graph api) and we saw that sometimes the first one is not being set. (the second and the third are set correctly). On the browser version of Outlook this never occurs, but with New Outlook for Windows it happens pretty regularly.
We get our auth token through MSAL.

axios
.patch(
${microsoftGraphAPIUrl}${messageId},
{
singleValueExtendedProperties: [
{
id: 'String {00020386-0000-0000-C000-000000000046} Name ' + name,
value: value,
},
],
},
{
headers: {
Authorization: 'Bearer ' + authToken,
'Content-Type': 'application/json',
},
},
)

Could this be related to an incompatibility between New Outlook for Windows and Microsoft Graph?
If you need further details please let me know,

主要语言
TypeScript
星标
833
派生
240
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

  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 摘要。