Function URL response streaming with small payloads unexpected behavior

Open
#102 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws, typescript
Domain
api, backend, cloud

Research direction

No file, test, or entry point is named. Reproduce the issue with Function URL streaming responses below and above 100 KB, then trace the runtime behavior around chunk delivery and framing. Done means small payloads arrive complete and correctly ordered, or the limitation and workaround are clearly documented.

Written by the indexing model from the issue text.

Description

We noticed that with payload smaller than about 100kb response streaming is not working properly: in some cases the chunk is buffered and sent with the next one, other times it appears incomplete or malformed. The workaround is to add some characters to reach a bigger size and get the chunk immediatly.
I can't find this limit mentioned in documentation.

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.