No error occurred; the request completed successfully. This value is unrelated to the HTTP 200 OK status code.

The request URL is malformed or otherwise invalid; depending on the platform, a bad URL might instead surface as HttpError.DnsResolve or HttpError.ConnectFail.

The hostname in the request URL could not be resolved via DNS.

The client failed to establish a TCP connection to the remote host.

The client ran out of memory while processing the HTTP request or response.

The request did not receive a response within the allowed time limit.

The server returned more redirects than the client is configured to follow.

The server returned a redirect response with an invalid or malformed Location header.

A general network-level failure occurred that does not fall into a more specific error category.

The HTTP request was aborted before it could complete.

The TLS/SSL handshake with the remote server failed during connection establishment.

The server's TLS certificate could not be verified.

An error occurred that does not map to any other HttpError value.

The connection was closed by the remote end before the full response was received, typically indicating a server or network problem.

An HTTP/2 protocol-level error was returned by the server.

The request was sent from a non-live environment (such as Studio) and the target service does not support creator environments.

A streaming request timed out because no data was transferred during the inactivity window.

The request was rejected because the client has exceeded its limit for concurrent or pending requests.

The server returned an invalid response to a ranged HTTP request, such as responding with a full 200 status instead of the expected 206 Partial Content.