Set caching headers on autocomplete

[GoogleCodeExporter]

* What steps will reproduce the problem?

Watch HTTP traffic for 
http://footprint2009qa.appspot.com/autocomplete/query?q=foo

* What is the expected output?

Sensible caching headers (either complete headers to mark it uncachable, or 
some reasonable time to cache it.

* What do you see instead?

Partial no-cache headers.

* Suggested fix from Adam:

Use versioned URLs, then set very long cache headers per version.

Original issue reported on code.google.com by matthew....@google.com on 16 Jun 2009 at 9:12

[GoogleCodeExporter]

Original comment by adam.sah on 24 Jun 2009 at 10:26

• Added labels: Milestone-Release1.6

[GoogleCodeExporter]

Original comment by adam.sah on 24 Jun 2009 at 10:35

• Added labels: Priority-Medium
• Removed labels: Priority-High

[GoogleCodeExporter]

Original comment by adam.sah on 25 Jun 2009 at 6:01

• Added labels: GoodStarterOr20PctProject