fix: streaming issue fixed for build versions

[thecodacus]

Fix Chat Streaming in Production Environment

Summary

Fixed real-time message streaming in production by correctly configuring Content-Type headers for Server-Sent Events (SSE).

Problem Description

The chat interface was experiencing inconsistent behavior between development and production environments:

• Development (wrangler dev): Messages streamed correctly in real-time
• Production: Messages only appeared after the entire stream completed
• User experience was degraded due to lack of real-time updates
• Console logs showed chunks arriving all at once instead of streaming

Root Cause Analysis

Server response headers were incorrectly configured:

// Previous configuration
return new Response(stream.readable, {
  status: 200,
  headers: {
    contentType: 'text/plain; charset=utf-8'  // Incorrect content type
  },
});

This caused:

• Browsers and proxies to buffer the response
• Stream chunks to be accumulated before delivery
• Loss of real-time streaming capability

Solution

Updated response headers to properly indicate Server-Sent Events:

return new Response(stream.readable, {
  status: 200,
  headers: {
    'Content-Type': 'text/event-stream',    // Correct SSE content type
    'Connection': 'keep-alive'              // Maintain connection
  },
});

Technical Details

• Server-Sent Events (SSE) protocol is used for real-time streaming
• text/event-stream Content-Type signals that the response should be processed as a stream
• Browser automatically handles chunking and parsing of SSE data
• No changes required to client-side stream handling code

Testing Performed

• Verified streaming in development environment (wrangler dev)
• Verified streaming in production environment
• Confirmed message chunks appear in real-time
• Tested with varying message lengths
• Verified console logs show proper chunk timing
• Checked browser network tab for correct headers

Impact

• Real-time message updates now work consistently across all environments
• Improved user experience with immediate feedback
• No buffering or delay in message display
• Reduced memory usage by processing chunks as they arrive

Rollback Plan

If issues are discovered, we can revert to the previous content-type by changing the header back to text/plain; charset=utf-8.

[johnykes]

still not working

[thecodacus]

still not working

what is your setup and issue ?
can you try the latest docker image

[johnykes]

still not working

what is your setup and issue ? can you try the latest docker image
Coolify. Tried using Docker, also using dev / prod commands directly

[thecodacus]

sorry I mean to say can you try this command
docker run ghcr.io/stackblitz-labs/bolt.diy:42030e1

[johnykes]

sorry I mean to say can you try this command
docker run ghcr.io/stackblitz-labs/bolt.diy:42030e1

thanks, but I have some custom edits:)

[johnykes]

but even with the 2 headers mentioned in #1060

responseHeaders.set('Cross-Origin-Embedder-Policy', 'require-corp');
responseHeaders.set('Cross-Origin-Opener-Policy', 'same-origin');

the problm persists for me.

It also uses https using CloudFlare tunnels.

[1394862250]

may you can try append one host ,just like 192.168.1.9 myblot.local，you need use .local that is importent
if you use powershell on window , you can try this conmend
Add-Content -Path "C:\Windows\System32\drivers\etc\hosts" -Value "192.168.1.9 myblot.local"