I’ve deployed an app bun-static-host and you can access one of the domains here: https://first.flycd.dev/
On my local machine response streaming works and I see Transfer-Encoding as chunked. However, it doesn’t work when I deploy to fly.io. Is this because of Fly Proxy zstd compression?
I read an old post where this got fixed for brotli compression or perhaps fixed in general but it seems not to work for me. Are my doing something wrong?
Try adding Content-Encoding: identity header
I did, and it made no difference.
I have a deep dive demo in five different runtimes: Deep dive demo · Fly Docs ; the premise of the demo is that you literally talk into your microphone and record audio streams that are saved to tigris where they can be played back.
The “Node.js” demo is not particularly Node.js specific, it likely will run as is on Bun. And you don’t need to bother creating a whisper machine for transliteration; the demo will work without it.
Perhaps you can try it out and see what is different? Last time I tried it, it was known to work, but if something broke in the meantime, let me know and I will dig in deeper.
I believe it’s something at the proxy level. If I run it local I see the response return Transfer-Encoding: chunked. But not when I deploy on fly. I’ll check again to see if there’s something i can do from my own side.
Here’s the response headers I’m seeing with my app, and it works:
HTTP/2 200
x-powered-by: Express
content-type: audio/mp4;codecs=opus
date: Tue, 21 Jan 2025 21:28:45 GMT
server: Fly/a3e18ae92 (2025-01-16)
via: 2 fly.io
fly-request-id: 01JJ5C94ENQ5QZY93YP9Y044N8-iad
X-Firefox-Spdy: h2
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.