WebTransportError
Baseline
2026
Newly available
Since March 2026, this feature works across the latest devices and browser versions. This feature might not work in older devices or browsers.
Secure context: This feature is available only in secure contexts (HTTPS), in some or all supporting browsers.
Note: This feature is available in Web Workers.
The WebTransportError interface of the WebTransport API represents an error related to the API, which can arise from server errors, network connection problems, or client-initiated abort operations (for example, arising from a WritableStream.abort() call).
Constructor
WebTransportError()-
Creates a new
WebTransportErrorobject instance.
Instance properties
Inherits properties from its parent, DOMException.
sourceRead only-
Returns an enumerated value indicating the source of the error—can be either
streamorsession. streamErrorCodeRead only-
Returns a number in the range 0-255 indicating the application protocol error code for this error, or
nullif one is not available.
Examples
js
const url = "not-a-url";
async function initTransport(url) {
try {
// Initialize transport connection
const transport = new WebTransport(url);
// The connection can be used once ready fulfills
await transport.ready;
// …
} catch (error) {
const msg = `Transport initialization failed.
Reason: ${error.message}.
Source: ${error.source}.
Error code: ${error.streamErrorCode}.`;
console.log(msg);
}
}
Specifications
| Specification |
|---|
| WebTransport # webtransporterror |
Browser compatibility
| desktop | mobile | server | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
WebTransportError
|
|
|
|
|
|
|
|
|
|
|
|
|
|
WebTransportError() constructor
|
|
|
|
|
|
|
|
|
|
|
|
|
|
source
|
|
|
|
|
|
|
|
|
|
|
|
|
|
streamErrorCode
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Legend
Tip: you can click/tap on a cell for more information.
- Full support
- Full support
- No support
- No support
- User must explicitly enable this feature.