As part of the API specification, some input parameters can have the location set to headers (as opposed to the typical header). From what I can tell, this feature is currently used for the S3 service only.
The headers location type specifies a prefix that can be used by clients to pass custom headers. For example, in S3, given the parameter:
Right now headers parameters are ignored, so users are not able to specify them. This PR adds support for headers input parameters and, therefore, for S3 metadata.
For now I only addressed the Erlang side. It would be good if some Elixir member could take that part, otherwise I will attempt it as a follow up.
As part of the API specification, some input parameters can have the location set to
headers
(as opposed to the typicalheader
). From what I can tell, this feature is currently used for the S3 service only.The
headers
location type specifies a prefix that can be used by clients to pass custom headers. For example, in S3, given the parameter:Users can specify metadata for uploaded files, as following:
Which will then be translated into the headers:
Right now
headers
parameters are ignored, so users are not able to specify them. This PR adds support forheaders
input parameters and, therefore, for S3 metadata.For now I only addressed the Erlang side. It would be good if some Elixir member could take that part, otherwise I will attempt it as a follow up.