BAD_AUTHENTICATION
When logging error responses, clients may always log the status code, domain, and reason.
-For errors with domain grpc.chat.signal.org and reason CONSTRAINT_VIOLATED, clients should check the details field for a BadRequest proto. If present, they should log the field of each violation in field_violations.
For errors with domain grpc.chat.signal.org and reason CONSTRAINT_VIOLATED, clients should check the details field for a BadRequest proto. If present, they should log the field of each violation in field_violations.
In a partial or total server outage, the server may start rejecting new connection requests or terminating existing connections with an HTTP/2 GOAWAY frame with code 0x40.
+If clients receive a 0x40 GOAWAY they should retry connections with an aggressive exponential backoff.
A prioritized list of username hashes to attempt to reserve. Each hash must -be exactly 32 bytes.
A prioritized list of username hashes to attempt to reserve.
+
+ Message
+ ElementConstraint
+
+
Message
@@ -122,6 +131,180 @@
+
+
+ message ElementConstraint
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Field
+ Type
+ Description
+
+
+
+
+ 1
+
+ nonEmpty
+
+
+
+
+
+ optional
+
+ bool
+
+
+
+
+
+
+ 2
+
+ size
+
+
+
+
+
+ optional
+
+ org.signal.chat.require.SizeConstraint
+
+
+
+
+
+
+
+ 3
+
+ exactlySize
+
+
+
+
+
+ repeated
+
+ uint32
+
+
+
+
+
+
+ 4
+
+ e164
+
+
+
+
+
+ optional
+
+ bool
+
+
+
+
+
+
+ 5
+
+ base64url
+
+
+
+
+
+ optional
+
+ bool
+
+
+
+
+
+
+ 6
+
+ range
+
+
+
+
+
+ optional
+
+ org.signal.chat.require.ValueRangeConstraint
+
+
+
+
+
+
+
+ 7
+
+ identityType
+
+
+
+
+
+ optional
+
+ org.signal.chat.require.IdentityType
+
+
+
+
+
+
+
+
+
+8
+
+ specified
+
+
+
+
+
+ optional
+
+ bool
+
+
+
+