简体繁体 English

SSRS电子邮件报告作业对PDF使用错误的内容类型

[英]SSRS email report job uses wrong content type for PDFs

原文 2017-04-07 18:59:19 4 1 email/ pdf/ reporting-services/ reporting-services-2012

I have SSRS (2012) configured to auto send reports in PDF format. 我将SSRS（2012）配置为自动发送PDF格式的报告。 In GMAIL (android), you cannot click on the reports to open. 在GMAIL（android）中，您无法单击要打开的报告。 You need to save to drive and then open from drive. 您需要保存到驱动器，然后从驱动器打开。 (outlook can open it though) （虽然可以打开它）

I think the problem is the content type is wrong. 我认为问题在于内容类型错误。

It sends out as: Content-Type: application/octet-stream; 它发送为：Content-Type：应用程序/八位字节流； name="application/pdf" NAME = “应用/ PDF”

It should be: Content-Type: application/pdf; 它应该是：Content-Type：application / pdf； name="application/pdf" NAME = “应用/ PDF”

Can anyone assist on how to fix this? 谁能协助解决此问题？ thanks, Zev. 谢谢，Zev。

headers from email. 电子邮件标题。 This is the PDF attachment SSRS attached when it sent it. 这是发送时附带的PDF附件SSRS。

----boundary_2_ee6bd0fc-4e77-432e-81f4-b678737c8c05 Content-Type: application/octet-stream; ---- boundary_2_ee6bd0fc-4e77-432e-81f4-b678737c8c05内容类型：application / octet-stream; name="application/pdf" Content-Transfer-Encoding: base64 Content-ID: <770d9496-f9ed-45cf-8e20-37667a2cd081> Content-Disposition: attachment; name =“ application / pdf” Content-Transfer-Encoding：base64 Content-ID：<770d9496-f9ed-45cf-8e20-37667a2cd081> Content-Disposition：附件； filename="=?utf-8?B?RW1wbG95ZWVzQ2xvY2tlZEluRHluYW1pY0dyb3VwaW5nUmVwb3J0LnBkZg==?=" 文件名= “=？UTF-8 2 B 4 RW1wbG95ZWVzQ2xvY2tlZEluRHluYW1pY0dyb3VwaW5nUmVwb3J0LnBkZg ==？=”

1 个解决方案

According to this post , the e-mail gets the wrong content type when it gets' modified post-SSRS: 根据这篇文章，电子邮件在修改后的SSRS后收到错误的内容类型：

Update on this - after much experimentation I found that the e-mail gets malformed when something is modifying it in transit after it has left the SSRS server (ie gateways adding disclaimers). 关于此的更新-经过大量的实验，我发现当电子邮件离开SSRS服务器（即网关添加免责声明）后，在传输过程中对其进行修改时，该电子邮件变得不正确。

This doesn't explain why the issue only seems to have started with SSRS 2012, though. 但这并不能解释为什么该问题似乎仅始于SSRS 2012。