[remoting host] Set the http user-agent in third-party token verification requests |
|||
Issue descriptionCurrently, the host process uses an empty User-Agent field when submitting third-party auth tokens for verification. It would be useful for logging/auditing if we included an identifying application name and version.
,
May 17 2016
,
May 18 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/4bacbb1c3ee8c1a0978e10bfe8e5c921ed775354 commit 4bacbb1c3ee8c1a0978e10bfe8e5c921ed775354 Author: lambroslambrou <lambroslambrou@chromium.org> Date: Wed May 18 19:38:21 2016 [remoting host] Add User-Agent to third-party cert validation requests. This sets the User-Agent to the application name (Chromoting or Chrome Remote Desktop) and version number. BUG= 611107 Review-Url: https://codereview.chromium.org/1987863002 Cr-Commit-Position: refs/heads/master@{#394507} [modify] https://crrev.com/4bacbb1c3ee8c1a0978e10bfe8e5c921ed775354/remoting/host/token_validator_factory_impl.cc
,
May 18 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by jamiewa...@chromium.org
, May 12 2016Owner: lambroslambrou@chromium.org
Status: Assigned (was: Untriaged)