Function URL with Response Streaming does not support Content-Encoding

Open
#96 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
aws, node.js
Domain
backend, cloud

Research direction

The issue names no repository files or tests. Start by reproducing the provided Node.js streamifyResponse example and inspect the response received through the Function URL; done means the gzip-compressed stream remains compressed and the Content-Encoding header is preserved.

Written by the indexing model from the issue text.

Description

If I compress my response using gzip and set a proper Content-Encoding response header, it appears like Function URL will decompress my response on-the-fly, remove the Content-Encoding header, and pass down the uncompressed response stream. This is wasteful and unnecessary.

const pipeline = require("util").promisify(require("stream").pipeline);
const { Readable } = require("stream");
const zlib = require('zlib');

exports.handler = awslambda.streamifyResponse(async (event,
responseStream, context) => {
    responseStream = awslambda.HttpResponseStream.from(responseStream, {
      statusCode: 200,
      headers: {
       'content-encoding': 'gzip',
       'content-type': 'text/plain',
      }
    });

    await pipeline(
      Readable.from(zlib.gzipSync('hello world')),
      responseStream,
    );
});

See here - the response is uncompressed, with Content-Encoding header stripped:

ss

Dominant language
TypeScript
Stars
224
Forks
60
Avg merge
26m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-lambda-nodejs-runtime-interface-client

All issues in aws/aws-lambda-nodejs-runtime-interface-client

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.