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
..
daemon	Move 'phd parse-commit' to a dedicated script; allow message parsing tasks to	2011-04-02 13:23:22 -07:00
mail	Fix a small inbound email glitch	2011-05-05 16:13:15 -07:00
repository	Open database connection with 'w' instead of 'r' for writing	2011-05-02 13:31:12 -07:00
search	Rought cut of search.	2011-02-14 15:34:20 -08:00
sql	Improve schema upgrade workflow for unprivileged users	2011-04-30 00:50:48 -07:00
user	Basic create_user script plus rough system agent support.	2011-04-12 18:34:53 -07:00
__init_env__.php	Fix a small inbound email glitch	2011-05-05 16:13:15 -07:00
__init_script__.php	[phabricator] Allow missing dependency checks to run	2011-04-30 14:38:09 -07:00
celerity_mapper.php	Allow Celerity to return "304 Not Modified" responses	2011-05-10 14:33:11 -07:00