Project

General

Profile

Feature #763

Add new endpoint configuration option "addHeaders" to add arbitrary HTTP headers to responses

Added by Chad Trabant about 8 years ago. Updated about 8 years ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
Start date:
01/13/2016
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

A concept for consideration:

Add a new endpoint configuration option "addHeaders" that is set to a list of HTTP header keys and values that are included in every response. The header values may include a small list of simple substitutions.

The configuration option is conceived as:

<endpoint>.addHeaders = \
key: value, \
key: value

where the key-value could be, for example:

@Content-Disposition: attachment; filename="binary.data" 
or
Access-Control-Allow-Origin: *

In most or all cases any headers specified through this configuration option should take precedent to any headers generated by WSS.

History

#1 Updated by Chad Trabant about 8 years ago

The example in the initial description came out poorly formatted.

Here is a more complete example of specifying two headers to be added to responses, in this case for the query endpoint:

query.addHeaders = \
  Content-Disposition: attachment; filename="binary.data", \
  Access-Control-Allow-Origin: *

#2 Updated by Mike Stults about 8 years ago

  • Resolution set to Fixed
  • Target version set to 2.0

The new parameter "addHeaders" is implemented and ready to test. These substitutions, ${appName} and ${UTC}, may be used in value field of a header.

Also available in: Atom PDF