Avoid XSRF initialization requests by using one token for the context
By using a single XSRF token for the entire web application context
we can avoid needing to issue a dummy POST, wait for an XSRF reply,
then reissue the real request every time we want to use a new proxy
we haven't touched yet. This speeds up many of the response times
by cutting out a full round-trip.
We can improve on that further by embedding a valid XSRF token in
the host page, as part of the state data we pass down into the
client UI.
Signed-off-by: Shawn O. Pearce <sop@google.com>
5 files changed
