[omaha] r172 committed - Edited wiki page ServerProtocolV3 through web user interface.

[om...@googlecode.com]

Revision: 172
Author: waf...@google.com
Date: Wed Apr 22 19:42:19 2015 UTC
Log: Edited wiki page ServerProtocolV3 through web user interface.
https://code.google.com/p/omaha/source/detail?r=172

Modified:
/wiki/ServerProtocolV3.wiki

=======================================
--- /wiki/ServerProtocolV3.wiki Thu Apr 2 18:02:01 2015 UTC
+++ /wiki/ServerProtocolV3.wiki Wed Apr 22 19:42:19 2015 UTC
@@ -430,6 +430,7 @@
* `X-Proxy-Retry-Count`: On a retry, contains the number of times an
HTTP 407 status code was received.
* `X-Retry-Count`: The total number of times that this network request
has been retried (e.g. using different proxy settings, different DNS
servers, or simple retries).
* `X-Request-Age`: The presence of this header indicates that this
request originally failed to send, and was persisted and later retried. The
value of the header is the time interval in seconds between the client's
current time and the client time at which the request was originally
attempted.
+ * `X-GoogleUpdate-Interactivity` -- Either 'fg' or 'bg' when
present, 'fg' indicating a user-initiated foreground update. 'bg' indicates
that the request is part of a background update. If the server is under
extremely high load, it may use this to prioritize 'fg' requests over 'bg'
requests.

Omaha Client uses CUP to secure the request and response. The following
request headers are used to implement CUP:
* If-Match: A signature that proves that the client knows the client's
private key.