magus v0.4.3 is out. See what's new
¶ View markdown source · ✎ Suggest an edit

MGS9028: streaming unsupported

The server answered 500 internal because the route streams Server-Sent Events and the response writer it was handed cannot flush.

[MGS9028] the response writer cannot stream; a proxy or middleware is buffering it
  see: .../MGS9028.md

Why

An event stream is useless if a layer holds it until the response ends. The route checks for the ability to flush before it writes a header, and refuses rather than open a stream nobody will receive.

Resolution

Reach the server directly on its loopback address, or configure the layer in front of it not to buffer (X-Accel-Buffering: no for nginx, response buffering off for other proxies).

What this is not

  • Not an internal read failure. That is MGS9027.
MGS9028apissestreaming500
Last updated (8b20a199)
Earlier changes on this page (1)

Full history ↗ · Blame source ↗

Glossary

Op

A single tool-native command a target composes (long form: operation); the middle of the work hierarchy (Spell to Op to Target). See operations.

Server

The background process a person starts with magus server start. It serves MCP, the console, background jobs and the warm knowledge graph, and adopts nested magus calls into one pool. See server.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.