[OAK-8104] [Direct Binary Access] DataRecordDownloadOptions should properly support filename* for Content-Disposition

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.10.0, 1.12.0, 1.14.0, 1.16.0, 1.18.0, 1.20.0
• Fix Version/s: 1.22.0
• Component/s: blob-cloud, blob-cloud-azure, blob-plugins
• Assignee: Matt Ryan
• Reporter: Matt Ryan
• Created: 04/Mar/19 15:54
• Updated: 11/Dec/19 21:21
• Resolved: 11/Dec/19 21:20

Description

OAK-8013 implemented a workaround for an issue in direct binary access where the "filename*" portion of the specified Content-Disposition header was being improperly set, and could not be fixed due to an issue with the Azure SDK.
This issue is created to properly fix the "filename*" portion for both AWS and Azure so it works as it should.

Issue Links

• is blocked by: OAK-8607 Undo workarounds for improper Content-Disposition support
• relates to: OAK-8013 [Direct Binary Access] DataRecordDownloadOptions creates invalid Content-Disposition headers - Workaround

Sub-Tasks

• Undo workarounds for improper Content-Disposition support: Resolved