Metadata of a message or a chunk of a message.
| JSON representation |
|---|
{
"userKey": {
object ( |
| Fields | |
|---|---|
userKey |
|
userAgent |
|
clientIp |
IP address where the message is created/updated. dot-decimal notation is expected, such as 100.2.3.4. |
timestampMicros |
The time when the user created the current version of the content. In other words, the last time this content is modified by the user. Note: a client should try its best to fill this field whenever a content is sent to AbuseIAm, both in ClassifyMessage RPC and as a response to RetrieveMessage RPC. |
headerOrder |
Header order of the http request from client. The header order is a string where each character in the string is an abbreviation of a field name in the header of the http request, and the ordering of these characters represents the ordering of the fields within the request. With each request the set of fields and their ordering within the request may change. Header order field abbreviations and names: A accept C cookie E accept-encoding F x-forwarded-for H host I if-modified-since K keep-alive L accept-language N connection R referer S accept-charset U user-agent V via Example header order: ARLEUHNKC This is an optional field that is send to AbuseIAm to help fighting spam. Details about the header order is here: https://cs.corp.google.com/p#google3/logs/gws/gwslog.proto&q=headerorder&l=1175 |
deviceIdHash |
Mobile Device ID. One way hash is required. The device id is expected to be a hex encoded MD5 hash of the actual device id. |
networkId |
Mobile Network ID - Identifies the network the mobile device is operating on. |
os |
Contains the operating system of the client. Typically used by mobile clients to specific the mobile OS. |
oauthTokenTimestampMicros |
Timestamp(in micros) at which the last OAuth Token was issued. This will be used by content that comes from APIs and will typically be used to prevent replay attacks. |
source |
Where does the request come from? e.g. gmail, webspam, aol, etc. The source is a unique identifier for a service that calls AbuseIAm. |
UserKey
All users are identified by a user (service, id) tuple. The service field is used to guarantee uniqueness over services. It is essentially the same proto defined in kansas/rpc/client.proto, but proto2 cannot depend on proto1 in proto_library.
For gaia user, the id shall be a hex value. More info is available at: https://sites.google.com/a/google.com/kansas/Home/kansas-client-documentation/kansas-developers-guide Note that we prefer hex without prefix padding of 0s, such as f48eaa2, instead of 000000000f48eaa2.
| JSON representation |
|---|
{ "service": string, "id": string } |
| Fields | |
|---|---|
service |
|
id |
|