addFileAttachmentAsync附加无效的授权头 [英] addFileAttachmentAsync Appends Invalid Authorization Header

问题描述

我正在开发一个应用程序，该应用程序的功能之一是使用Office.context.mailbox.item.addFileAttachmentAsync将文件附加到外发电子邮件中.在最新版本的Outlook for Windows版本1811(内部版本11029.20079，即点即用)中，文件无法附加到邮箱项目，并且UI中显示下载错误".

I work on an application that as part of one of its features attaches files to outgoing emails with Office.context.mailbox.item.addFileAttachmentAsync. In the most recent update Outlook for Windows Version 1811 (Build 11029.20079 Click-to-Run) the files are failing to attach to the mailbox item with a "Download Error" displayed in the UI.

为了进一步检查此问题，我使用了Fiddler，并发现此方法已开始附加以下标头Authorization: Bearer.由于未提供头授权，因此该冲突会导致S3服务出现问题，并返回400错误Only one auth mechanism allowed;，这将导致下载失败.

To inspect this further I user Fiddler and discovered that this method has started appending the following header Authorization: Bearer. Since no header authorization has been provided, this conflict causes trouble with the S3 service and a 400 error Only one auth mechanism allowed; is returned which would cause the download to fail.

是否有解决此问题的方法?

Is there a workaround to this problem?

推荐答案

@Kevin Kerr，感谢您报告此问题.

@Kevin Kerr, thanks for reporting this issue.

这是在我们的API之外重现的已知问题.您可以通过手动将此项目附加到电子邮件来重现此内容:打开新电子邮件，单击Attach File，然后单击Browse This PC...，然后将文件的URL复制/粘贴到File name Insert File对话框打开的字段.

This is a known issue that reproduces outside of our API. You can reproduce this by manually attaching this item to an e-mail: Open a new e-mail, click on Attach File, then click on Browse This PC..., and then copy/paste the URL of the file into the File name field of the Insert File dialog that opens up.

Azure Blob存储也会重现此问题，因此最好的解决方法是将文件托管在其他位置.

This issue also reproduces with Azure Blob Storage, so the best workaround is to host the files elsewhere.

我们已经聘请了适当的团队来解决此问题，但是，我们没有针对此问题的预计到达时间.

We have engaged the appropriate team to address this issue, however, we don't have an ETA for the fix.

这篇关于addFileAttachmentAsync附加无效的授权头的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！