Skip to content

Interface: ErrorFrame

The bridge's report that a frame this browser sent did not go upstream.

Sent only to the browser that sent the frame, and never for something the bridge accepted. The socket stays open. Silence would be worse than the frame: a write that is refused (no upstream connection, a full outbox, a message kind a client may not send) is not retried anywhere, so a browser that hears nothing has no reason not to believe it landed.

Properties

code

code: string

A stable machine-readable reason, e.g. not_connected.

event

event: "error"

message

message: string

Human-readable detail, suitable for a UI log.

tag?

optional tag?: string | null

The rejected message's INDI tag, or null if it did not parse.