PR https://github.com/GoogleCloudPlatform/cloud-run-proxy/pull/25 removed population of the "Authorization" header by default.
While X-Serverless-Authorization should be used by default, it breaks pre-existing compatibility with services which perform additional authentication/authorization using the "Authorization" header. To allow for these scenarios, I've added a "use-authorization-header" flag, defaulted to false. When set, it will populate the "Authorization" header in the outgoing request instead of "X-Serverless-Authorization".
PR https://github.com/GoogleCloudPlatform/cloud-run-proxy/pull/25 removed population of the "Authorization" header by default. While X-Serverless-Authorization should be used by default, it breaks pre-existing compatibility with services which perform additional authentication/authorization using the "Authorization" header. To allow for these scenarios, I've added a "use-authorization-header" flag, defaulted to false. When set, it will populate the "Authorization" header in the outgoing request instead of "X-Serverless-Authorization".