Whitelist custom headers for Assets

[#1]

Request for Feature Enhancement (RFE) Summary:	Allow custom headers with dynamic value for assets to be added from AEM (for example, set header in the filter).
Use-case:	Integration of 3rd party search solutions to index content for search, for example AddSearch, but can be extended to any use case when custom header is needed. In case of AddSearch, pages are indexed by adding HTML meta tag, but for the assets this approach is not feasible. To enable indexing for the assets, HTTP header needs to be added as described in https://www.addsearch.com/docs/indexing/defining-custom-fields/ . Value of the header is dynamically defined by application (for example contains document type and file name).
Current/Experienced Behavior:	HTTP Headers are not present in the response. Filter is triggered and solution works fine on the Local SDK (screenshot attached), displaying proper values both on publish and dispatcher. Header is removed when redirecting asset request towards binary bucket.
Improved/Expected Behavior:	Clients are able to define custom headers whitelist so header added from the AEM is present in the asset response.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM as a Cloud Service SDK version is not relevant
Customer-name/Organization name:	ASSA ABLOY
Screenshot (if applicable):
Code package (if applicable):

[#2]

Hi @daspicko 

I like the idea and I am curious further how that can be implemented and made available to AEM users. Shell it be like visual capabilities to manage assets headers ?

[#3]

@daspicko 

Thanks for proposing this idea.

This has been reported to the engineering under the internal reference ASSETS-46188. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.