[MGNLDAM-530] ContentDisposition header cannot be disabled Created: 10/Dec/14  Updated: 05/Jun/15  Resolved: 12/May/15

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: 1.1, 2.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Haaris Mohammed Assignee: AntonĂ­n Juran
Resolution: Not an issue Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

As per guide Content-Disposition header can be disabled for paths based on patter.
But this is not working - header still exists.

http://documentation.magnolia-cms.com/display/DOCS/Digital+Asset+Management+module#DigitalAssetManagementmodule-Contentdisposition

Magnolia Version: 5.3.5



 Comments   
Comment by AntonĂ­n Juran [ 12/May/15 ]

Not an issue, if configured more than one voter under contentDisposition node, is necessary to add here op property with and value (an operator between voters). Was updated in documentation, see link: https://documentation.magnolia-cms.com/display/DOCS/DAM+core+functionality.

Generated at Mon Feb 12 05:00:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.