epriestley e27c5f26e5 Allow Celerity to return "304 Not Modified" responses ... Summary: We always return HTTP 200 right now and don't send a "Last-Modified" header, so browsers download more data then necessary if you sit on a page mashing reload (for example). Test Plan: Used Charles to verify HTTP response codes from 400, 404 and 304 responses. Mashed reload a bunch and saw that the server sent back 304s. Changed the resource hash seed and saw 200s, then 304s on reload. Reviewed By: tuomaspelkonen Reviewers: tuomaspelkonen, jungejason, aran CC: bmaurer, aran, tuomaspelkonen Differential Revision: 253		2011-05-10 14:33:11 -07:00
..
api	PhabricatorEnv	2011-01-31 11:55:26 -08:00
controller	Allow Celerity to return "304 Not Modified" responses	2011-05-10 14:33:11 -07:00
map	Bring Javelin into Phabricator via git submodule, not copy-and-paste	2011-05-08 13:20:10 -07:00
response	Bring Javelin into Phabricator via git submodule, not copy-and-paste	2011-05-08 13:20:10 -07:00