@@ -29,6 +29,7 @@ public enum CefErrorCode
2929 // 600-699 <Obsolete: FTP errors>
3030 // 700-799 Certificate manager errors
3131 // 800-899 DNS resolver errors
32+ // 900-999 Blob errors
3233
3334 /// <summary>
3435 /// An asynchronous IO operation is not yet complete. This usually does not
@@ -185,10 +186,8 @@ public enum CefErrorCode
185186 /// </summary>
186187 BlockedByCsp = - 30 ,
187188
188- /// <summary>
189- /// The request was blocked because of no H/2 or QUIC session.
190- /// </summary>
191- H2OrQuicRequired = - 31 ,
189+ // NET_ERROR(H2_OR_QUIC_REQUIRED, -31) was removed. It was:
190+ // The request was blocked because of no H/2 or QUIC session.
192191
193192 /// <summary>
194193 /// The request was blocked by CORB or ORB.
@@ -265,7 +264,8 @@ public enum CefErrorCode
265264 SslClientAuthCertNeeded = - 110 ,
266265
267266 /// <summary>
268- /// A tunnel connection through the proxy could not be established.
267+ /// A tunnel connection through the proxy could not be established. For more info
268+ /// see the comment on PROXY_UNABLE_TO_CONNECT_TO_DESTINATION.
269269 /// </summary>
270270 TunnelConnectionFailed = - 111 ,
271271
@@ -659,6 +659,37 @@ public enum CefErrorCode
659659 /// </summary>
660660 EchFallbackCertificateInvalid = - 184 ,
661661
662+ // Error -185 was removed (PROXY_TUNNEL_REQUEST_FAILED).
663+
664+ /// <summary>
665+ /// An attempt to proxy a request failed because the proxy wasn't able to
666+ /// successfully connect to the destination. This likely indicates an issue with
667+ /// the request itself (for instance, the hostname failed to resolve to an IP
668+ /// address or the destination server refused the connection). This error code
669+ /// is used to indicate that the error is outside the control of the proxy server
670+ /// and thus the proxy chain should not be marked as bad. This is in contrast to
671+ /// ERR_TUNNEL_CONNECTION_FAILED which is used for general purpose errors
672+ /// connecting to the proxy and by the proxy request response handling when a
673+ /// proxy delegate doesn't indicate via a different error code whether proxy
674+ /// fallback should occur. Note that for IP Protection proxies this error code
675+ /// causes the proxy to be marked as bad since the preference is to fail open for
676+ /// general purpose errors, but for other proxies this error does not cause the
677+ /// proxy to be marked as bad.
678+ /// </summary>
679+ ProxyUnableToConnectToDestination = - 186 ,
680+
681+ /// <summary>
682+ /// Some implementations of ProxyDelegate query a separate entity to know whether
683+ /// it should cancel tunnel prior to:
684+ /// - The HTTP CONNECT requests being sent out
685+ /// - The HTTP CONNECT response being parsed by //net
686+ /// An example is CronetProxyDelegate: Cronet allows developers to decide whether
687+ /// the tunnel being established should be canceled.
688+ /// </summary>
689+ ProxyDelegateCanceledConnectRequest = - 187 ,
690+
691+ ProxyDelegateCanceledConnectResponse = - 188 ,
692+
662693 // Certificate error codes
663694 //
664695 // The values of certificate error codes must be consecutive.
@@ -1202,12 +1233,12 @@ public enum CefErrorCode
12021233 /// The IP address space of the cached remote endpoint is blocked by private
12031234 /// network access check.
12041235 /// </summary>
1205- CachedIpAddressSpaceBlockedByPrivateNetworkAccessPolicy = - 384 ,
1236+ CachedIpAddressSpaceBlockedByLocalNetworkAccessPolicy = - 384 ,
12061237
12071238 /// <summary>
12081239 /// The connection is blocked by private network access checks.
12091240 /// </summary>
1210- BlockedByPrivateNetworkAccessChecks = - 385 ,
1241+ BlockedByLocalNetworkAccessChecks = - 385 ,
12111242
12121243 /// <summary>
12131244 /// Content decoding failed due to the zstd window size being too big (over 8MB).
@@ -1512,5 +1543,54 @@ public enum CefErrorCode
15121543 /// requested probe record either had no answer or was invalid.
15131544 /// </summary>
15141545 DnsSecureProbeRecordInvalid = - 814 ,
1546+
1547+ /// <summary>
1548+ /// Returned when DNS cache invalidation is in progress. This is a
1549+ /// transient error. Callers may want to retry later.
1550+ /// </summary>
1551+ DnsCacheInvalidationInProgress = - 815 ,
1552+
1553+ // The following errors are for mapped from a subset of invalid
1554+ // storage::BlobStatus.
1555+
1556+ /// <summary>
1557+ /// The construction arguments are invalid. This is considered a bad IPC.
1558+ /// </summary>
1559+ BlobInvalidConstructionArguments = - 900 ,
1560+
1561+ /// <summary>
1562+ /// We don't have enough memory for the blob.
1563+ /// </summary>
1564+ BlobOutOfMemory = - 901 ,
1565+
1566+ /// <summary>
1567+ /// We couldn't create or write to a file. File system error, like a full disk.
1568+ /// </summary>
1569+ BlobFileWriteFailed = - 902 ,
1570+
1571+ /// <summary>
1572+ /// The renderer was destroyed while data was in transit.
1573+ /// </summary>
1574+ BlobSourceDiedInTransit = - 903 ,
1575+
1576+ /// <summary>
1577+ /// The renderer destructed the blob before it was done transferring, and there
1578+ /// were no outstanding references (no one is waiting to read) to keep the
1579+ /// blob alive.
1580+ /// </summary>
1581+ BlobDereferencedWhileBuilding = - 904 ,
1582+
1583+ /// <summary>
1584+ /// A blob that we referenced during construction is broken, or a browser-side
1585+ /// builder tries to build a blob with a blob reference that isn't finished
1586+ /// constructing.
1587+ /// </summary>
1588+ BlobReferencedBlobBroken = - 905 ,
1589+
1590+ /// <summary>
1591+ /// A file that we referenced during construction is not accessible to the
1592+ /// renderer trying to create the blob.
1593+ /// </summary>
1594+ BlobReferencedFileUnavailable = - 906 ,
15151595 } ;
15161596}
0 commit comments