commit d1efb45fec665e82680f992e01a5900f3c7f0d72
author David Pletcher <dpletcher@google.com> Tue Sep 01 17:45:55 2015 -0700
committer David Pletcher <dpletcher@google.com> Fri Sep 04 16:11:50 2015 -0700
tree ce039696765cc77dac73611d55748cb802f681a3
parent 40b7472fef771105bce10048e87ab63686305b18

Implement Safe Content REST API method

The Safe Content REST method has similar behavior to the legacy
CatServlet servlet. It retrieves the requested content directly,
for safe file types, or as a ZIP file containing an entry with
an unpredictable filename based on the resource filename.

There are minor differences. RestApiServlet always specifies
attachment, with or without a filename, for the Content-Disposition,
whereas CatServlet would not declare direct downloads as attachments.
Given that the attachment disposition is obligatory, this REST API
method always sets a meaningful attachment filename, for ZIP files
and direct file alike.

RestApiServlet specifies and parses resources differently than
CatServlet. The GetSafeContent view includes an optional parameter
for naming the side, which becomes a suffix decorating the filenames.
CatServlet will use this parameter to designate whether the file
comes from a child or parent in a diff.

A forthcoming patch will modify CatServlet to consolidate its
implementation, taking advantage of this new code.

Change-Id: I2ecdbd0bd6706066026000de813244f909d48cba