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

Function URL with Response Streaming does not support Content-Encoding

Abierto
#96 1 comentario 1 reacción 0 asignados Ver en GitHub
Lenguaje dominante
TypeScript
Estrellas
224
Forks
60
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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.

```js
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](https://github.com/aws/aws-lambda-nodejs-runtime-interface-client/assets/10402560/984abcb7-b4d9-4402-b96d-ccbf9f30bb64)

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.